The next item of business is portfolio question on the rural economy. I'll try and get all questions and supplementaries into how people are succinct. First is Willie Rennie. Oedden I—to ask the Scottish Government what discussions it's had with the fishing industry regarding compensation arrangements in relation to the impact of offshore windfarm developments? Fergus Ewing. The Scottish Government has been working closely with the fishermen and stakeholder o daoddiad Personal frofod? Mae'n gweithio gan gweithio iddo aww addysbrush o'iIfard blaenau fyrmaiddio i gyda infrastructure datblyg lleidwadol yn CM tofu. Mae r working partnerships appear yn ddiwed Dancing thosedod yng nghymru wedi bod yn clarity mewn defnythg accommodate Alun Arnau yn gwneud y byddiig iaailr rainbow rymell gydaredd rogfa wedi mwyfyrnau ei ddafnog iawn. Taeth dwy rymell gyda symud cyfrochu ar ôl oedd yn merddwyr oedd, dros andygol, yn teimlo maesio. Mae cofiosio iddyn nhw. Ar ddechrau'r ffaithol gofyn, mae ffaithwyr yn bwysig. Roeddwch chi'n mwyfyrnau ei ddafnogi a dw i ffaithwyrnau rogfa wedi mwyfyrnau. Cali dddid o erbyn ei ddyn nhw, yn mynd i iechidio'r ffaithwyr yn gweld g Goldfinch. I have met with some of the fishmen, some of them in Pittenweem, on the 15th of April. I listened carefully to their concerns about lack of engagement in relation to cable burial and route and timescale of works. My behest officials had a follow-up meeting with them on the 30th of April. I understand that a further meeting is taking place with Marine Scotland officials, developers and fishmen in Pittenweem tomorrow. I am determined that we find a solution that allows both renewables and the fishing sector to thrive and flourish. That means very careful consideration of the cable issue in particular. I undertake to Mr Rennie and to Mr Gethyn, as the MP has raised the matter with me, that I will consider those matters very carefully, working with my colleague Paul Wheelhouse, for safety grounds and for avoiding damage to fishing gear. It is extremely important that the burial of cable takes place wherever possible and practical. The direct route of that is something that I would expect to be considered extremely carefully indeed. After all, the fishermen were there first. Given that the fishermen have in-depth knowledge of where the best fishing grounds are, would it not be more effective just not to cite new developments where those grounds have been identified in the next rounds of offshore wind? I certainly agree that it is sensible that those involved in both sectors should communicate closely with each other. After all, as Maureen Wattwell knows, the fishermen have extensive and detailed knowledge of the seabed in their areas. That is knowledge that if there is proper collaboration between them and the renewable sector, it could be put to good use. Scottish ministers use a process of sector marine planning to identify future areas for commercial-scale offshore wind developments. That is considered, a wide range of data and illustrates where fishing takes place as part of an overall analysis of opportunities and constraints. Therefore, I believe that those matters are required and are in fact the subject of proper and appropriate consideration during the development process. To ask the Scottish Government what its plans are for farm safety week 2019. The Scottish Government works closely with partners such as the health and safety executive to provide support and guidance to farmers, to their employees and families to help to make farms safer environments to work and live on. We are also involved in the Scottish Farm Safety Partnership, which is committed to reducing farm work place fatal accidents by 50 per cent by 2023. The farm safety week to which the member eludes will seek to highlight the importance of the issue, and we are considering the role that the Scottish Government might play this year. The NFUS has already issued a call for examples from farmers of how it has made safety improvements on farm and, more importantly, the inspiration behind those changes in behaviour. Alison Harris I thank the cabinet secretary for his answer. Only a month ago, two people were killed as a result of a tragic accident on a farm in my constituency of Central Scotland. In light of the fact that it is child safety week this week, could I ask the cabinet secretary if the Scottish Government had made provision for children's safety on our farms? Fergus Ewing I am aware of the incident to which Alison Harris eludes that this was a tragic accident where two men died after a well-collapsed farm, and our thoughts go out to the families involved. It illustrates that fatalities and serious injuries in farms are very serious matters. Of course, as the member appreciates, the prime responsibility for safety lies with employers, to properly look after ourselves and those for whom we are responsible. It needs to be said that that principle is never going to change. The health and safety executive is a reserved body, but we work closely with it. We fund or part fund organisations such as Lantra, which provided training courses in the central belt this year in Dumfries, in respect of areas such as falls from heights and falling objects, cattle, vehicles and machinery. However, I am pleased to have the opportunity to answer Alison Harris, because this is probably the area of life in Scotland where there is still a far too high level of injuries. Of course, any death is one too many. Emma Harper There are around 1,000 injuries in two deaths each year as a result of a quadbike accident in Scotland. The cabinet secretary might be aware of my on-going campaign to encourage quadbike wearin, which is called the quadbike helmet wearin. I therefore ask the cabinet secretary if he will join me in encouraging farmers and agricultural workers to wear helmets both on and off the road. Would he be open to meeting with me to discuss potential action that the Scottish Government can take to further this aim? Liam Vercushwing Yes, I am aware of the risk of those who drive on quadbikes without wearing helmets.  I commend Emma Harper for her campaign on this, and I would be very happy to meet her and discuss what, if anything, further we can do. Willie Coffey To ask the Scottish Government whether it will provide an update in progress being made on payments to farmers. Fergus Ewing We have made 17,749 basic payment scheme loan offers worth over £343.6 million in the autumn last year, earlier than in previous years, which put cash into the rural economy ahead of any other part of the UK. Basic payments for 2018 started on 19 March, with more than £14,300 payments worth £289.8 million made to date. I am pleased to say that we are on track to deliver both pillar 1 and pillar 2 payments in line with the schedule that was published in December last year, and we are also on track to meet our regulatory target of making 95 per cent of pillar 1 payments by the end of this month. Willie Coffey For that answer, he will be aware of the uncertainty that is being caused by Brexit to sheep farmers, including those in my constituency. What is he doing to ensure that they have the financial support that they need in these uncertain times? Fergus Ewing I am acutely aware of the uncertainty that is caused by Brexit and the worries that are faced by our sheep farmers and our hill farmers in general. That is a very serious issue indeed, and I am pleased that Mr Coffey has raised it. Willie Coffey We announced the LFASS loan scheme in March, giving eligible farmers and crofters access to 90 per cent of their LFASS payment. That has been appreciated as a practical measure. In addition to that, I have repeatedly pressed the UK Government, along with my Welsh and Northern Irish colleagues at the meetings that I attended with Ms Gougeon and the UK ministers, including Ms Gougeon, that there should be a properly-funded, treasury-funded compensation scheme in the event of a no-deal. However, a no-deal would be utterly catastrophic for our hill farmers and sheep farmers in particular, and therefore I very much hope that it will be averted. Rhoda Grant Because of the climate crisis, farmers and crofters need to know what assistance is going to be available to them to reach net zero. Will the cabinet secretary, as a matter of urgency, bring forward a new scheme that helps them to achieve that goal? Rhoda Grant We set out our plans in our document stability and simplicity. Those plans provide something that, with respect, is not provided to the counterparts elsewhere in the UK, namely the relative confidence that the existing support that is enjoyed by Scottish farmers and hill farmers in particular will continue. I think that that is the most important thing. We also, in the second part of the five-year period of stability and simplicity, have set out in that document stability and simplicity our plans that we will pilot ways in which to promote even more sustainable farming. However, I am convinced, as I discussed with Martin Kennedy, whom I met last week at a hill farm in Aberfeldy, that the work that farmers do shows that they are part of the solution, not part of the problem, and that mixed livestock production, sustaining as it does ruminants on our hill sites, sequester carbon in permanent grassland. If it was not for that activity, as many members in the chamber know better than I, there would be devastatingly bad consequences through the loss of that carbon sequestration. It is our duty to get positive messages about farming's existing contribution to the climate that is better understood and acknowledged. Donald Cameron I refer to farming and crofting in my register of interest. Does the cabinet secretary who mentioned ELFAS in one of his answers acknowledge the comments from the NFUS less favoured area committee chair, Robert MacDonald, who said that a bigger funding issue for our hill farming and crofting sectors is potential cuts to ELFAS in 2019 and 2020? Can the cabinet secretary give us an update, and especially reassure those worried farmers and crofters on this particular matter? Fergus Ewing Yes, I know Robert MacDonald well and have met him and his colleagues. He chairs the ELFAS committee of the NFUS on several occasions. In fact, I met the NFUS just yesterday again and discussed this. I am very pleased that this year we maintained ELFAS at 100 per cent, even though our ability to do so only became evident at the relatively late period in the financial year. We were able to maintain that. This year, I believe that it is the case that I think that 56 per cent of ELFAS recipients have received more than they received before slightly. Mr Cameron asked about the next two years. The EU rules provide that the payments must be reduced over the next two years. I have indicated that we wish to do everything that we can to find a workaround to prevent that from happening. It is a very technical and complex area, not made any simpler, I have to say, or easier by the fact that we do not actually know whether we are going to be in or out of Europe and therefore we do not know which rules will apply. However, be all that as it may, I will do my very best to ensure that our whole farmers receive the support that my goodness me, they earn. Questions and particularly answers, Cabinet Secretary, are getting a bit lengthy if we are to get through this. Question 4, Margaret Mitchell. To ask the Scottish Government whether it will provide an update on the work of the Scottish partnership against rural crime. The Scottish partnership against rural crime continues to play a valuable role in bringing together key partners from across the rural and justice sectors to tackle all forms of criminality in our rural communities. The partnership recently produced its rural crime strategy 2019-2022, highlighting its focus on tackling serious and organised crime as it affects rural communities. Work is also under way to strengthen local approaches to tackling rural crime across Scotland. Earlier this year, the cabinet secretary participated in the launch of the new East Lothian partnership against rural crime, led by East Lothian council, and a similar initiative is just about to begin in Tayside. That will bring together local authorities, police and other partners to strengthen the local approach to rural crime. In April, my ministerial colleague, the cabinet secretary for culture, tourism and external affairs, participated in the launch of a new Scottish heritage crime group that is formed under the auspices of spark to tackle crime against our historic and cultural sites. Margaret Mitchell. I thank the minister for that comprehensive answer. Should we be aware that the rural economy is negatively impacted by rural crimes such as livestock worrying and theft, but also by flytaping, which has a hugely detrimental impact on the farmers, landowners and local authorities that have to bear the cost of cleaning up those sites? In order to address those worrying and escalating problems, will the minister support my campaign, which includes giving local authorities, agencies, occupiers or owners of land the same powers as their counterparts in England and Wales, to make compensation orders to recover the costs and cards for clearing those sites? I am glad that Margaret Mitchell raised the serious issue, because flytaping is a serious issue in rural areas and it seriously blights our countryside as well. My ministerial colleague is the cabinet secretary for the environment, climate change and land reform, who has portfolio responsibility for the issue. I know that the cabinet secretary would be happy to consider the proposals that are being suggested by Margaret Mitchell, because I think that this is a very serious issue that we need to take a look at. If there are other powers that we can look at that would help to tackle this, that is what we need to consider. 5. Keith Brown To ask the Scottish Government what information it has regarding the progress being made with the review of intra-UK allocation of domestic farm funding that is being led by Lord Bewe. The review panel has been taking evidence, including from me, and I understand that it is close to making its final recommendations. Progress is, however, being hampered by the UK Government, as Michael Gove has confirmed in writing that he is not prepared to release to the review panel previous advice to ministers. That is disappointing, as he promised this information not only to me but to Scottish stakeholders in a public debate that I had with him. I raised this when I met the panel on 15 May and made clear that in any future funding arrangements, whether in the UK or the EU, it would be totally unacceptable if Scotland continues to receive payment at the lowest rates per hectare of any country in Europe. It is a quite outrageous situation. I thank the cabinet secretary for his response, and I ask whether that means that there have been no assurances from the UK Government that the £160 million that is denied to farmers in Scotland, including those in my constituency, will be returned to Scotland, that a future funding formula will be fair to Scotland's interests, and that the full value of current direct farm support will be provided by the UK Government to the Scottish Government after 2022 once its guarantee runs out. Well, Mr Brown is absolutely right to raise this. This is money that was intended by the EU for Scottish farmers and to which only Scottish health farmers were entitled, and the UK Government diverted this money away from them to a tune of £14,000 for every farmer and crofter in Scotland. That is quite a scandalous act by the UK Government, and Mr Gove promised that the review that was first indicated by Owen Paterson in 2013 would be implemented. He was overruled by the Treasury, who overruled him and said that he could not do that. The review is now only looking at two years and not at what happened and to explain why that happened and why our farmers were deprived of that money. The fact that the UK Government is concealing the evidence about the advice given to them on the basis of which they took the decision to divert that money away from Scottish health farmers and crofters is one of the most disgraceful acts in Government that I have come across in my 20 years as an MSP. To ask the Scottish Government whether it can provide an update on the work of the Orkney-native wildlife project and what it is doing to support the project's objectives. The Orkney-native wildlife project is being led by Scottish Natural Heritage and the RSPB, and it has been in discussion with local representatives of the National Farmer's Union of Scotland about establishing a land access protocol governing the setting of traps for stotes on agricultural land. Jamie Halcro Johnston I thank the minister for that, and I would like to draw the chamber to my register of interest. The project's work to control stotes is currently at a standstill, with many local farmers still refusing access to the land because the anger of their concerns over geese numbers are not being properly addressed. Farmers are looking for a clear indication that the Scottish Government understands the problem, that they appreciate the damage that the geese are doing, and that they will act on geese numbers. Deputy Presiding Officer, failure to get stote traps in place in the next few months could lead to an explosion in numbers. So can the minister outline what actions she can take and what resource she can allocate to support efforts to control the geese population in Orkney, and in order to break the impasse before the summer, which she considers incentivising farmers to provide access with a bounty on stotes trapped on their land? Mairi Gougeon That is an issue that I would be happy to discuss further with the member if he would like to have a meeting with me to discuss that. I know that Scottish Natural Heritage has convened an Orkney goose management group to investigate how future adaptive management of grey lag geese can be supported, so that is being looked at. As a partnership, the group will look to develop, agree and implement additional measures to reduce the impact of the resident geese population. If the member would like a meeting, I would be more than happy for that to take place. Liam McArthur Short supplementary would be appreciated, please. Liam McArthur Thank you, Deputy Presiding Officer. I welcome that commitment to a meeting from the minister, as Jamie Halcro Johnston has indicated. There is anger at the contrast between the funding for the stoke programme and the withdrawal of funding for the goose management programme, so I think that it would be helpful if the minister were able to discuss with us how the work of that goose management group can now be supported, including funding being made available. Mairi Gougeon Again, I would extend that same offer to Liam McArthur as well to see how we can move this forward. Mairi Gougeon Thank you very much. There are two members who I have not been able to call—Rona Mackay and Tom Mason—and I apologise for that. Can I say to all members that I do not want to be cutting people off in their prime, either when they are asking questions or when they are answering, but what we had there were quite a few speeches rather than questions. Can I ask that perhaps people discuss us within their groups with a view to making sure that everyone gets an equal opportunity to take part in these questions and answer sessions? That concludes portfolio questions. We will move on to the next item of business. If everyone would like to shift their seats accordingly.


Good afternoon everybody. Thanks for attending the last session. I'm going to present a new project. I call it only BC and you can access the presentation including the source code in the URL. The URL is, I think it's quite easy to remember, it's just the same as the library name. I'm Jun Huang and my experience was, I was a contributor of AOSP since 2010. I already contribute for more than 50 contributions to AOSP. Also I'm co-founder and developer of LSD which is the library desktop environment. Besides that, I was the developer of the Naro working on Android platform. My employee history including MediaTek and IQQ. So I'm going to discuss about based on my experience, I would like to talk about the idea to reuse the Android for ordinary linear space products. And so I will discuss about the C-Library Toolchain Optimization and Confluent Group for a long time. Before this session, you can refer the related talks including Android Builder Summit. The LLB and Linux, this one is very interesting. And you can refer to Torbath and the memory allocation including this afternoon K Configure. So there are four parts in my talk. The first one is we are going to analyze how we can benefit from Android. Then we can make a new project, I call it old EBC. So the project goal is to be configurable. And then we apply some optimization techniques. The last one is an action item which is something I didn't complete yet. So the first one I will talk about how can we benefit from the existing Android infrastructure. Including Bionic, LibreC, DynamoLink and some debugging facilities. So you already know Android is not linear. But our plan is to take something useful back to embedded linear. Yesterday, Roy had an excellent talk. He mentioned that Debian is the new long batch and Bionic LibreC is just a long time to to excuse the new long batch. So Bionic is very interesting because Google already modified heavily to fit its requirement. So why should we choose Bionic as the base for our new project? I think the first one is very important, the license. So if you compare some existing open source projects, GDBC is GPO, microcontroller LibreC is LGPO, Dial LibreC is GPO, Muscle LibreC is MIT. That's good. But if you check the implementation, you can see if you compare some target like the lattice on MIPS and Intel OTAN. You can see GDBC does optimization pretty well and microcontroller LibreC does some simple optimization. But Dial LibreC does nothing for optimization. Muscle LibreC only does the simple Intel architecture optimization, mainly in Mathematica. You can notice that Bionic has better API coverage by versions. And it already can run some complex applications like LibreOffice and FIFAS browser already. So I think the Bionic LibreC is getting better.  The upstreaming is, I mean the progress of upstreaming is always slow. But you can see it's a potential benefit. So if we can propose a new open source project to merge this effort, that should be very interesting. So the goal of LibreC is pretty straightforward. So first to create small, fast and standard compliant implementation of C-Library. Also, we offer the configurable some option to configure the implementations. So you can configure from very small implementation to smartphone-like devices. Also, we pick out all the system components, for example, benchmarking validation or even prelinker from Android as the base. We can merge some security enhancement or fixes from other open source projects like NetBSD, FreeBSD, even some CVE fixes. You might know from several vendors like STL, NVIDIA, TI, and other SOC vendors, they all have git repository or other open source repository. So it is very interesting if we can introduce all the enhancement into the single source tree. So let's review the programming model first. As soon as there is a hardware program, so you can see you use a compiler to generate the EF image file, and then program loader load it to memory. So you can see some sections like state of BSS data and the text.  But for some environment like Android, it's multi-threaded, so you can see it's going to be more complex. And if you compare Linux and Android, you will find that the basic component, I mean the kernel and the library, are almost the same. And there are just some minor differences. So our idea is we try to move something interesting, something useful back to embeddedness, so from the right side to the left side. So let's review Bionic libc. It is a small C-diver implementation, which is a mixture of NetBSD and FreeBSD. FreeBSD, the inclusion of FreeBSD is pretty new. It is about last year in AOSP master branch, especially for the libn implementation. Bionic libc is majorly in BSD license, which has partially portless compliance, not compatible to GDC, and there is no system 5 IPC support, because Android engineers think that they are superior, I mean there is a replacement called Bind IPC. For AOSP master branch, there are mainly three targets. One is with stumble support, and Intel X86 and MIPS target. In the past, there is even a super-h architecture support, but the architecture support was removed about two years ago. Also Bionic libc has fast pith-ray implementation based on few tests. So if you compare the full-point, you can see GDC, micro-control libc and Bionic, if we compare some older versions, you can see quite a large difference. So GDC is one megabyte, but Bionic libc is only 243. Bionic libc has some limitations, so you can see there is no complete wide critical support, and there is no full C++ section support, and there is no fully C++ STL, and no fully POSIS support. If you check the source tree, you will notice that there is a very important description about memory map. So before Android 4.0, the memory map is fixed, so you can see the linker and the native library along with the Java occasions. They all have fixed address. But after Ice Cream Sandwich, which is Android version 4.0, the memory map is already changed. So let's check the changes. Since Android 4.0 Ice Cream Sandwich, there is a new mechanism called AOR, which stands for address-based layout randomization. So it advances security enhancement, which is known to protect system and third party application from attacks. Also, since Android 4.1, there is a new mechanism, PIE support. You can notice that the original prelinker, EF prelinker was removed since Android 4.0, because the memory layout is totally changed. Since Android 4.1, there is an interesting feature called address sanitizer. Adress sanitizer is a special memory long-time memory checker. So we can compare if it's wagering. So you can see it can perform some checking. For example, hip-out bound check, stake-out bound check. And the OHA is very, very low compared to wagering. So you can enable the feature. You can enable the feature and check some output like this. If you have a buggy program like this, it's buggy because there's free. So the system will dump this useful information. So you only have to add one line, this line in file android.mk and then address sanitizer will be automatic enabled. So this is a reference output. So you can see there is a buggy program. It's our range memory access. So you can see the memory checker detects the problem for the address. Also, we can check the share library implementation in Android. The older Android dynamic has some problem which limits the number of share library to 128. And since last year, finally, there is a change which allows dynamic allocation. So you can see Android Bionic has long history if we count it from Android team. So it's from 2005. So seven years past, the diamond link already has no such restriction. This is very interesting. And you can see from other open source project like Mozilla or LibreOffice, how can they overcome such problem? They use extra HEC copy of Bionic library. So if you download a Firefox browser in your mobile phone, there are two dynamic link at the same time. It's ridiculous, but it is a problem. So you can see from the above description, Bionic has some good part like this. This is good. And Bionic has some short part like this. And you can see about C++ integration. There are already several solutions. So if you check the NDK, you can see the comparison. By default, there is no C++. I mean, there is no fully C++ port. But you can use some extra packages like STL port. So STL port does not support C++ exception, but support C++ RTTI, which stands for long-time identification in current Android configuration. Also, you can use GANU-STL packaging, which supports both C++ exception and RTTI. To simplify the porting effort, we only provide, only the C++ only provides STL port. And it depends on the wide correct support in C library. Also, there is an interesting component in Android called Debuggedy, which is embedded-specific cache candler. So it can correct the crash data in certain files. And also, in addition, Debuggedy can also facilitate committing Debuggedy to a dyeing process. So you can correct the information before a process being dyeing. And it is a BISD license. How it works? Basically, Debuggedy has a crash handler demon. Also, it has a default signal handler to each process, which handles any signal that is generally called, I mean, the cooldown. So you can think about the interaction between Diamond Linker and Debuggedy. So once the default signal handler is registered, when application is going to dye, so you can catch the information. So the signal handler captures the information and contact Debuggedy. So Debuggedy can use its built-in on-stack unwinder to generate backtracks. This is very important for Android tracing, because you have to couple with both Java and the native long time. So usually C and C++. It's a common technique that if you want to trace running Java problem, you can trigger a signal to access Debuggedy to capture the backtracks. And you can even ask GDB to attach. And the Linalo compiler, sorry, Linalo Toolchain Working Group improved Debuggedy two years ago. So the improved one can generate more specific backtracks information and even has better integration with GDB. Timber of Sony improved Debuggedy. So he took the code base from Android and applied to ordinary Linux. So he created a new project called Crash-led Candler, which is based on Debuggedy, but it can correct more information. So you can see Android's Bionic C is not only C implementation, it has some useful utility, like Debuggedy, like Azure's standard title, and some security enhancement. And about the license issue, there are several articles discussing about the way Google works around GPL, because Google used a script to pass the header file and generate the constant. Google engineer, sorry, Google claimed that the generate file is not a copyright, but someone, if you are interested, you can read the articles, the two articles. It is still a potential problem that the way Google to work around GPL license might be a problem, because they didn't do a curriculum process. But we think the way Google does is acceptable. I mean, you can check the license. So after all the policy is generated, you can check the file, for example, LibreC. So if you check the LibreC file, you can see the complete license noticement. And the Linux kernel header is just regarded as the generate information instead of the copyright material, according to Google's statement. To eliminate the problem, we just follow the way Google does. So if you have any suggestions, please discuss with us. Okay. So let's think about how to make a configurable C library implementation. So we are talking about this area is C long time, which talks to kernel as the interface of application. The first problem we encountered is the broken tool chain. So what's that? In fact, there are several utility to generate tool chain. So you can see there is a close tool. There is even close to a new next generation. And many commercial tool chain like code software. So there are many, many tool chain. And there are even LLVN-based tool chain. But Android has only one tool chain support. It's one Google engineer maintenance. So if you want to replace the default tool chain to other tool chain, to replace the built-in Google tool chain with code-associated tool chain, or other commercial tool chain, or even the tool chain you built from scratch, you might encounter the problem about the incompatibility. Before looking into the issue, let's check how tool chain works. So in the diagram, the blue one is GCC, and the red one is Bing utility, and the green one is C library. So you can see GCC is just a compiler driver which talks to several components like C preprocessor and C1, which is the real C compiler, and assemble and correct which merge these objects. And even talk to SLLD to generate the final EF image. And during the process you can see some components like CRT which stands for C runtime. And you might need some library, for example the EH, which stands for exception handling. So it's not simply a program, but a collection of several utility. This is tool chain. So you might encounter any problem resulting from every piece of the components. For example GCC found it might be crash. For example the linker might crash or generate the incorrect output. So the issues are as following. Code source tool chain doesn't use code linker as far as I know. I mean the last years release CSL9 is still BFD based GNU LD instead of golden. But Android original build flags are a bit aggressive and it applies ICF which is identical code folding which is golden linker only redundancy elimination. So you have to be very careful because Android has some aggressive flaggers. This optimization is good if your tool chain is well tuned and your source code is fixed some bugs. You can use ICF to search. I mean you can use ICF to search WebKit or you can search ICF. Oh sorry. Oh okay. Oh just ignore because it's empty. I didn't take the correct example but I have to remember that. In fact Google's optimization has some bugs so sometimes you have to work around. Okay I remember that. So if you search ICF you can see the ICF flag is set to save. ICF. But if you check the Git source tree you can understand the original configuration is ICF to all instead of ICF save. ICF all can bring the 5% size reduction but while ICF save is not. So this is a problem that Google's tool chain always applies aggressive optimization and it changes so fast. But if you use external tool chain you have to turn off the optimization but while you turn off the optimization your code might not run because Google engineer always tests one tool chain at one time. So that is a problem which leads to the extra effort for olibacy if we want to support several external tool chains as the normal open source project does. Okay let's review the procedure to build an Android compatible tool chain. You have two ways to build a tool chain. One way is bell bone style or bell mental style tool chain. You have to work with Android tree I mean the fully the full source tree and specify all system and the bionic header including several libraries and even Google's workaround. Also you can prepare standalone style building so it just looks like a traditional tool chain like code source tree tool chain but this is changing if you check the source tree or Android tool chain. There is a repository called Android tool chain you can check out this is here. There is a manifest regarding the tool chain and you will find some interesting interesting target. That is there are more targets than you expect so you can see the read me has a full target but in fact the the maker file that iron has more more configuration and they are they are they are changes of face so that is a problem you if you take the second way you have to take care the configuration and that's a header file the library and everything to be compatible with Android tool chain. So after the analyzing we get out to be fully compatible with Android tool chain we want to use the external tool chain instead of the Android Android building one so we just fix the this I mean we did some hacks but I don't have enough time to talk about that so it takes time to do some hacks so let's continue. The goal of all the machine is configurable on the optimize so there is menu configure like system so you can you can see like this sorry for that okay so you can you can enable because you can choose the target and even enable some some SOC optimization like quarkon quarkon crate or quarkon scope here and it might imply some internal rule for example the neon and you can even enable the debugging facility even adjust the alignment for memory allocator and even you can even ah sorry it's typo memory okay so you can enable the memory checking and some extensions and the build process will communicate to Android's build system we take some time to hack Android build system to be compatible with K config like system so you only have to modify one file you can check this so you only have to modify one file to press the description okay so the last part is talking about the optimizations in fact Android already applies several optimization techniques so the first one is the symbol visibility so you can see Android applied this this flag to enable the link object garbage collection so it's known to saving some libraries especially C++ library also the google engineer use a genetic programming to figure out the best fit compile time flakes so it's very crazy but this also a problem for the for the external toolchain for example the default configuration of code sorcery is already based according to mental graphics but if you apply these flakes the optimizer might crash or generate the long call because it is not the same code base of gcc so you have to be very careful about these flakes also there is an optimization called fdo which means feedback the rate of optimization the idea is very simple which is to correct your runtime information so it's a paradigm called build and build long build so you if you build the first time and the skill the is give you a program and optimize i mean the second build will will accept your profiling data and the the optimize again is called fdo so if you check the source code of all libc you can see fdo is enabled in our configuration already but it's still experimental it can bring some performance and the core size performance core size and even full-print optimization it's a visible enhancement also we have some diamond link optimization we improve that is common for gdbc but missing in bionic so we improve we implement that gnu style hash and improve the pre-linking so you can see from the diagram it's normalized so our final result is here so the diamond link link time is shortened and the symbol luga is is very very very small so the to do list is we want to follow the the way gdbc does that is to introduce option group based on portis spec so we can have better better configuration about the features about the extension of even the standard and we can write down the the the detail action item of fire sound issue if we can support such such such option groups and currently we are still working on these issues to resolve external toolchain issues we already verify console 3 toolchain but we still have some issue about the toolchain generated by bilroot or other other tool like open embedding i think it would be nice if we can collaborate with other open source project like cross tool bilroot yaktou and so on and we developed some validation tool my time is is is is up but we we modified and enhanced some some some tool so you can you can see like this we can perform some benchmarking so for example if we want to benchmarking the str len implementation you can compare gdbc and our our olibacy implementation so we want to make it more stronger and improve the unit test since we have to take take care about the standard compliance so you can compare another one is built by built by olibacy and we want to merge several more and more soc companies compute contribution so for example mvdr ti and st evison currently they do contribute to aosp but their their contribution are always wildly with each other because for example quarkon has different neon implementation so quarkon's neon optimization or quarkon's vfp optimization is not fitting the target of st evison not fitting the target ti so we want to build a a more flexible way to to let the configuration coexist and you can check the performance data is benchmarking so you can see the gdbc version compared to olibacy version so you can see the the throughput is is higher olibacy is higher than gdbc also we want to merge some open source projects for example open mp support the compiler already has has great open mp support for example gcc and even alvn but she long time has a jail jail is doomed to integrate such enhancement so that's our our our to-do list and reference okay i think my time is up


Climate models predict that global average humidity will increase by approximately 7%, which is consistent with the Clausius-Cloparin-CC equation. However, these models also predict that global precipitation and evaporation rates will increase by only about 2%. This suggests that the models may not accurately capture the full extent of the effects of increased humidity on climate. This article was authored by M. L. Roderick, F. Sun, W. H. Lim and others.


Hi, I'm Marie Bauer with CSIS Southeast Asia program, and I'm very pleased to have Sydney Jones from the International Crisis Group from Indonesia visiting us today. Sydney, welcome to Washington. Thank you. I'd like to ask a couple questions. Indonesia obviously has problems with homegrown terrorists, the bombings in Jakarta and Bali, or evidence of that. Can you tell us how you think about this issue and are there trends you can identify in terms of domestic terrorism and the government's progress in addressing these issues? Yes, I think the first thing to note is that it's not a huge issue. It's one that gets a lot of public attention, but I don't think it's something that most Indonesians worry about night and day. I think that there are, there have been major strides made in identifying some of the networks. The problem is that the ideology of what we call Salafi jihadism has taken root in Indonesia. So it's not easy to eradicate, but we're not seeing a huge drive for recruitment, and we are seeing some community pushback. So I would say it's a containable problem, but it's not going to go away anytime soon. Well, the US-Indonesian relationship is one the Obama administration hopes to elevate and even transform into a robust partnership. What are your views on the potential to enhance that relationship, particularly in the areas of military to military cooperation? And counter-terrorism cooperation? On counter-terrorism cooperation, there's no question but that the relationship is already close, and I think it will only continue to grow closer. The FBI is working very closely with the Indonesian police. There's been a lot of assistance in terms of training. I think there are a lot of people going to the United States for enhanced skill training and so on. So all of that is to the good. In terms of the military to military relationship, there's some outstanding problems. And I think one of the problems is a difference in views particularly between the US Congress and the Indonesians on the amount of accountability that can take place for past abuses. Frankly, I think no matter how hard the United States pushes, there is not going to be prosecutions for past abuses. I think there's too much resistance to that in the military and too much concern of not wanting to be seen to be pushed around by the United States. I think there is leverage that the United States could exert on moving forward with better accountability in the future, but only if you have a fully restored military relationship to start with. So, can I follow up on that? I mean, is it of enough value to push ahead and go ahead and reopen those ties if we're not going to get the sort of retroactive satisfaction that Congressman Leahy or Senator Leahy and others want to see? I think it's probably an important enough relationship to move forward, but it's ultimately a decision that the Indonesian government and the US have to agree to. And I don't think all of the interventions by non-governmental organizations are going to make much of a difference in that. I think there are a lot of people looking at Indonesia geostrategically who say, how can we not have a full military to military relationship? Recently, the Indonesian counter-terrorism forces killed several terrorists and uncovered plans for attacks in various places, including Singapore. How current is that threat now? I'm not sure that the threat to Singapore was more than just a document found. And I'm not sure there's any real substance to that, but I think that there is no question that some of the terrorists arrested in Indonesia had international linkages. And I think one of the things we need to know a lot more about is the exact nature of those linkages. One person now on trial in Jakarta was in regular communication, for example, with Al Qaeda in Pakistan. He wasn't part of this group that was arrested in Aceh, but I think part of the difficulty in understanding these networks in Indonesia is to know that it's not just one group. We've got lots of different groups, all small, all fringes of fringes of fringes, but all interested in continuing the Jihad. Thank you. Your group, the International Crisis Group, looks at areas of crisis and conflict in Southeast Asia. What are the areas of most concern to you now? And how would you prioritize these for U.S. policymakers working on the region? I think anybody looking at Southeast Asia today would see Thailand as the biggest problem that they're facing. And I think if you look in comparison to Thailand, the Philippines, even Malaysia, Indonesia looks like a rock of stability. Thank you very much, Sydney Jones. I appreciate your taking time with us. Thank you.


So I'm Chris Baer, one of the first residents here. I'm on the neurophthalmology rotation right now, so this seems like a good opportunity to present kind of a neurophthalmology-oriented case. So we're gonna look at a patient who presented with bilateral vision loss, a company with a headache. So I saw this patient on call in the emergency room. In brief, she's a 64-year-old woman with a history of headache and bilateral vision loss. She developed a severe headache while overseas. She described this headache as very sudden onset, very high intensity, unlike anything she'd ever had before. She went to the hospital there, very reasonable. She had an MRI that was normal, and the rest of her work up there was normal. She came back to the States, but her headache persisted. It wasn't quite as intense as it had been, but it was still persistent. And about 10 days later, she noticed a decrease in her vision. She went to the hospital, another hospital, here in the state.  Labs showed a mildly elevated ESR, and so she was discharged on prednisone with plan to follow up with her ophthalmologist to get a temporal artery biopsy due to concern for temporal arteritis. After starting the steroids for vision, actually continued to decline, and so she came to the university hospital, which is where I saw her. She had no GCA symptoms, no jaw claudication, weight loss, muscle weakness, any of GCA symptoms. And just interestingly, her blood pressure had been in the 140s to 150s systolic. She said she was your runs in the 90s, so it was a bit of a departure for her. Her past medical history was unremarkable, specifically no history of headaches from migraines, and her eye failure, she was notable for retinal tear in her left eye that she'd had fixed a couple years prior. No medications, no allergies, no family history, and no use of alcohol, tobacco, or recreational drugs. So on exam, she was hand motion in both eyes. Pupils were briskly reactive, there was no APD, her motility was full, her pressure was normal, and the rest of her exam was really fairly unremarkable. We saw laser in around a tear in her left eye that looked well sealed, but otherwise very unremarkable. And so, thinking about our differential at this point, there are a lot of things that can cause headaches, and there are things that can cause vision loss, but the things that combine the two, especially with headaches that are this severe, the list gets a little bit smaller. And things that we need to be thinking about, obviously when someone presents with a big, big severe headache like this, intracranial hemorrhage is obviously one thing that pops right to the top of our list. GCA is certainly something we could think about. Our CVS and PRAS are something we're gonna talk a little bit more about here in a few minutes. Vascularitis can also cause headache and vision loss like this. Much less likely, or migraine, especially without any previous history, clots, again, less likely, given no significant other risk factors for that. So this patient needs imaging, and so we were able to get that in the emergency room, and a couple of important things to note, it's not subtle here, you can see heroccipital lobes, these areas of pretty large infarction of both of heroccipital lobes are kind of what we're drawn to here. Over on the far right-hand side, we have vessel imaging, this is an MRA of her brain, and I don't know if we have a pointer here, let me see if I can just show you over here, maybe not, I'll just describe it to you. So we see some kind of subtle narrowing of her PCA arteries right here and here in this MRA image, and we also, not shown here, but we also had narrowing of her branches of her MCA as well, bilaterally. And so, she was admitted to the hospital with a little bit more workup, she initially had an elevated ANA, this was repeated and was later turned out to be a repeat negative. Her ESR I mean mildly elevated at 33, the remainder of her workup was negative, and she even had specific vessel wall MRI, which was read as normal, there was no signs of vascularitis or other inflammatory conditions on that vessel MRI. And so, for treatment, her steroids were stopped, this was not consistent with any kind of GCA diagnosis, she was started on nemotopy, which is a calcium channel blocker, and over the course of a few days that resolution of her headache. And so, this is a case that certainly has features that are consistent with RCVS and press, maybe a little bit less likely to see an espaculitis, but I thought this was a good opportunity to talk about RCVS and press, this is a, these are conditions that we don't necessarily talk too much about in our general ophthalmology world, but these patients can present to our clinic, and it's a good opportunity to really delve into this a little bit more and just review this, for not only for ourselves for boards, but also for clinical practice as well. So, RCVS is reversible cerebral vascular constriction syndrome, and this is one of those syndromes that's very, very aptly named. It's an encompassing term that encompasses a lot of, kind of a collection of different entities that were previously separate things as postpartum angiopathy, benign cerebral angiopathy. They're now kind of under this umbrella of this RCVS syndrome. The pathophysiology involves transient, reversible, narrowing of cerebral vasculature, and it's unclear what the precipitating event is in these. Some people have speculated that headaches will result in vascular narrowing. Some people say that it's the vascular narrowing that comes first, and so people are not necessarily sure, but we do see this transient, reversible narrowing of the cerebral vasculature. Women are commonly more affected than men. There's no really significant predilection for age or race in the literature. Risk factors for this can include things like pregnancy, vasoconstrictive drugs, specifically things like cocaine, heroin, marijuana's been implicated, SSRIs are another common implicating factor as well. If you have thrombosis, that can do it, and then migraine is also a risk factor as well. It's important to know that these are associated risk factors. Not a lot has been shown to prove causation of these things. The clinical presentation, typically, folks present with a sudden onset, very severe headache, unlike anything they've ever had before, folks who have migraines and other types of headaches note a very clear distinction between this type of headache and their typical migraine headaches. Typically, they're located occipitally and they can be associated with nausea and photophobia. They'll typically have periods of these intense pain followed by areas of relief. And so, like in our patient, her headache went down, never went completely away, but got better, and then they'll have exacerbations of this pain going back up to that severe level over the next few days to weeks. It's very rare for patients to have RCVS without a headache. Less than 10% of people in the literature have a subacute or not a very severe headache, and so that's one important diagnostic criteria here. Folk ulnar allergic symptoms can develop. Headache is the predominant symptom, it can be the only symptom in about a third to half of patients, but folk ulnar allergic symptoms can occur, specifically for us. Visual symptoms that we need to be looking out for could be things like scutomas, hemianopias, and then cortical blindness, or severely decreased vision, like we saw in our patient here. The diagnosis is made by a few different ways. Number one, we have to have a high clinical suspicion for this based on the clinical history and the presentation of this type of headache and symptoms. Laboratory testing for this is typically normal. There's really no, usually at laboratory abnormalities, including inflammatory and other labs. Imaging is important in this diagnosis. MRI is very important to look for areas of vascular narrowing, but it's important to know that in a lot of cases, up to 30 to 70% of cases, actually, their initial MRI will be normal, and we saw that in our patient here. She had an MRI on presentation when it first started that was normal, and then she also had to repeat imaging a few days later when she came here to Utah, that was also normal as well. And so neurovascular imaging is an important thing as well. So, MRA, CTA is an important tool that we can use, and the classic description when you do angiographies, you'll see this kind of sausage on a string pattern. This is really nicely highlighted up here in this picture labeled A on the far left. You can see these areas of vascular dilation and narrowing. Kind of looking like sausage on a string at a butcher shop if you've ever been to one of those places, but that's kind of the classic description right there. Here is a little bit closer up view, and you can see on the left-hand side here, these areas of vascular dilation and vascular narrowing. This is a little bit closer up picture. And then over on the right-hand side, you can see this is a reversible process. You can see the vascular shearers return back to its normal state. This is after a month later. And so the management for our CVS really resolves around supportive care. So you stop any inciting agents, stop the vasoconstrictive drugs if they're on anything, and then work on controlling blood pressure if their blood pressure is high. Now blood pressure can be a little bit tricky in this because hypertension, if the patients have hypertension, it can induce further vasoconstriction, which obviously we don't want. However, if you drop their blood pressure too low, it can result in hypotension, which can trigger ischemia. So it's kind of a fine balance to walk. Calcium channel blockers are kind of the mainstay of treatment that we use. There's a lot of evidence for things like nemotapine and verapamille as far as reducing the severity of their headaches and improving the overall symptoms. They don't necessarily impact the time course of vasoconstriction and getting back to normal vasculature, but symptomatically they can certainly improve the headaches that patients have. So it's a pretty controversial intervention. We don't use them typically, and they're certainly not our first line for this condition. And we stopped those when she came here to our hospital. And then in severe recalcitrant cases where they're having progression and significant neurologic symptoms, there's been case reports of actually doing intra arterial administration of vasodilators, which is also a little bit of a risky proposition. Your risk by doing that, intra arterial angiography certainly has its own risk, but directly infusing vasodilators also increase your risk of having a reperfusion injury in these patients. So it's a little bit tricky how to manage that. Prognosis of RCVS tends to be fairly good. Most people have resolution of their headaches and angiographic constriction within days to weeks. It is reversible condition. However, about 15 to 20% have residual deficits from strokes, and we saw that in our patient here. Most of those deficits are minor, but some can have severe deficits as we saw in our patient here. Flipping to a similar condition, it has some overlap with what we just talked about, press. So posterior reversible encephalabic syndrome is a syndrome defined by characteristic clinical features of neuro-imaging findings. As in RCVS, it's more commonly found in women than men, and it can't affect any age group. Patients as young as two have been reported, and as old as 90 have been reported throughout the literature. The pathophysiology, we see some similarities with RCVS, but there's some specific things to press when you talk about. First, there's impaired augurated auto-regulation on hypertension. If you remember back to medical school, you remember that cerebral perfusion is very tightly defined, and as systemic blood pressures rise and fall, the cerebral vasculature will constrict and dilate to maintain equal perfusion to the brain. When you get to extremes of that, you can have impaired auto-regulation that can lead to blood vessels not behaving in the ways they should. It can lead to increased pressure to the brain, which can lead to a leakage of blood products and causing a bedema in the brain. On the flip side, in other cases of press, we can see actually cerebral ischemia and vasoconstriction, which is actually a similar mechanism what we see on RCVS. And this is all highlighted by an ethyl disfunction allowing leaky and ethylion-aligned blood products to leak into the cerebral, to the brain parenchyma. Risk factors for press. So hypertension is the one we classically talk about. It's important to know not only absolute hypertension, which is an important risk factor, but also relative hypertension. So if someone runs in like our patient in the low 90s, for example, and her blood pressure suddenly spikes up to the 140s to 160s, relative hypertension can disrupt the auto-regulation, auto-regulatory mechanisms and can cause press. It's also been associated with renal disease, pregnancy, specifically folks who have preeclampsia or eclampsia. Immunosuppressive medications have been linked to it in autoimmune conditions. Things like rheumatoid arthritis, are also commonly described as risk factors for press. The clinical presentation, again, patients will present with headaches, but the headache in press tends to be a little bit more indolent than the abrupt onset kind of thunderclap headache that you see with RCVS. Patients will often present with visual disturbances and the disturbances can be similar. They can have heminobium, hallucinations, auras, and even portable blindness, like we saw. Patients will often present with seizures and altered mental status around sevelopathy. Imaging, the classic finding is posterior white matter edema. And you can see here, this is kind of a textbook picture of this edema in the posterior circulation right there. What we'll see is, you can't have involvement of other areas of the brain as well. You can't have lesions in the frontal lobes, although it's atypical to see involvement elsewhere in the brain without involvement in the posterior portion of the brain as well. On vessel imaging, vessel imaging can show vascular narrowing, similar to what we see in RCVS, which can make a little bit of diagnostic confusion then if we're not careful. Complications from press. So you can have ischemic complications and you also have intracranial hemorrhage. And this is showing press complicated by hemorrhage surrounding areas of edema right there. Hemorrhage can occur in as many as 20% of patients and it's really something that leads to a lot of morbidity in patients who have press. The management of press, number one, is controlling hypertension. And again, just as an RCVS, we have to be cognizant of how we control that hypertension. We don't want to drop them too low. We risk ischemia, but we can't leave them to high risk hemorrhage. Treatment of seizure is obviously important. Treatment of eclampsia if they're pregnant is very important. And then again, in this condition, just like an RCVS stores are not typically recommended. Steroids can negatively impact your blood pressure, making it difficult to predict where it's going to go. And so we typically don't use steroids in these cases as well. The prognosis, most cases of press are benign without lasting deficits. And it's reversible just like our CVS with symptomatic improvement, usually occurring before we see radiographic resolution of edema and things. The minority of cases, however, do have lasting neurologic deficits. And recurrence is uncommon. Thankfully, less than 10% of patients do have a recurrence. And so our patient here has features certainly of both. Her blood pressure was higher than it was in the past. She had vascular narrowing on imaging and certainly areas of infarction on imaging as well. And so the diagnosis for her is a little bit unclear, but the treatment for her either way would be the same. And this is an important thing because as ophthalmologists, patients will come in with visual deficits. And it's an important thing for us to be just cognizant of and to keep our differential because these things are diagnosed not only by imaging, but with clinical suspicion. And if we don't have that clinical suspicion, there's one thing that we could potentially miss. So this case was a good example to kind of review these conditions and just kind of refresh our memory on these things. Any questions? Great. So how common are these? This is really bizarre. A isolated, relatively brief period of focal dysautonomia. I mean, that's essentially what this is. And obviously pretty scary as you think about how this all evolves. I mean, Judith Howefin, do you see one of these cases? Do you see one of these once a year? Well, we don't see the vast majority of the cases in neuropomology because most people don't have any lasting deficits. But over at the hospital, they've got at least a couple of months. So this is what you're saying is this is certainly rare, but not uncommon. Right, yeah. And if you lump RCBS and press together, which radiologically I think that they think of them as kind of a continuum. They're both a dysautonomia of some sort. Well, and there's a predilection for the posterior circulation because the auto regulation of the posterior circulation is less robust than the anterior circulation.  So all kinds of weird eye movement abnormalities and things. Could be a real puzzle clinically to figure it out. But with all the young pregnant people, with all the people on the medications that are known to precipitate press, even over at primary, you'll see these conditions. And I mean, I can't really put a number on it, but I would say that at any given time, they probably have somebody in the hospital with it, whether it be on the OBGYN floor or in the medical ICU. In controlled blood pressure, they're a funding agent. Give them time, and it tends to resolve and not come back. Yeah, most of the time there aren't lasting deficits. But the presenting neurological symptom is frequently visual. Right. Well, you can see that. So funny spots in the vision, but their exam is normal. They may not have the fundus findings of hypertension. And in a child with this, their blood pressure may be 140. If their blood pressure is normally 90, 80, or 90 over a palp, as children often are, they can have this with what, to us, would appear to be a relatively normal blood pressure. Is it usually pretty symmetrical between the two Ys? Well, since it's cortical, mostly, yes. Turning where it is. Yeah, it's routinely spots in the vision. Chris, how's your patient? She improved it all. So she saw Dr. Warner on clinic. And essentially, her vision had actually improved a bit. She was able to say, I think, 2100, essentially. Her central vision hadn't gotten much better, but essentially, she was actually able to do visual field. So she can count fingers in the right superior and left inferior quadrant of both eyes. And yeah, she was actually able to see the eye chart, which there were tears of plenty, because she really had, she was functionally completely blind at onset. So we've got to move on. So if you would mind, you can set up. Just to answer this question, Chris, so you said, MRI could be normal in our CVS. What would you see differently for vasculitis versus the sausage on a string? Yeah, yeah, yeah. So with vasculitis, you can see similar findings. With vasculitis, you'll typically see also an ventilated inflammatory markers as well. With our patients, she had an elevated ANA, which raised concern for vasculitis. But repeat ANA was normal. Or see, your ESR is mildly elevated. But if you adjust it, it's not really that elevated. And actually, it might even be age-adjusted normal. You can see the usual thing with this kind as you jump to the heavy-heeled steroids. But that could make it worse.


from Las Vegas. It's theCUBE. Cover EMC World 2016. Brought to you by EMC. Now, here are your hosts, Stu Miniman and Brian Gracely. Welcome back to the Sands Convention Center here in Las Vegas. This is SiliconANGLE Media's flagship program, The Cube. We go out to the shows, help extract the signal from the noise. I'm actually remembering back to VMworld 2011, probably a yard or two away from where we are right now. We were doing a spotlight on service providers. That was the first time I was introduced to Virtue Stream and thrilled to have back on the program, Rodney Rodgers, the CEO of Virtue Stream. You know, Rodney, thanks for joining us. Always great to see you guys. So, what a whirlwind it's been, Rodney. You know, about a year ago it was announced that EMC was going to buy Virtue Stream. 10 months ago it closed over a billion dollars. Now Dell, you know, acquiring EMC.  Well, where are things going, you know, in your world these days? So, it's been a really busy year. Quite an extraordinary year. You know, through it all, we've maintained kind of our focus on our core, you know, go-to-market approach. The thing that's kind of defined us and led us, you know, find our seam in this marketplace to prosecute well against. And now it's really more of an issue of scaling that significantly. Our integration in EMC is largely complete. The integration, the planning process ahead of the potential closure of the Dell deal has been something that's been a bit of a lighter burden on us as you guys saw yesterday. You know, we're maintaining our operating identity as one of the Dell Technologies Group of companies and such. So, you know, Michael's been incredibly supportive of what we're doing and you know, his questions to me are more like what can I do to support you growing? You know, your growth, what are your impediments to growth? That type of thing. So, we have our charter. It's quite well-defined and you know, my mission is just to continue to prosecute it. You know. So, Rodney, the first day the press and analysts got a run-through of all the announcements. Right. And when it came to Q&A, you know, it was cloud, VirtuaStream, VirtuaStream. How's this fit? Can you walk us through, you know, what's new, what is just kind of emerging from stuff that you were doing before that now the various pieces that Dell EMC are taking advantage of? Sure. We have three infrastructures of service platforms. The first is what we call our VirtuaStream Enterprise Cloud. That is heritage VirtuaStream's platform. You know, our whole micro-VM technology, resource optimization, built for these IO intensive mission critical type of stateful workloads. That's kind of our core use case, our core go-to-market motion. Our VirtuaStream Federal Cloud is essentially the Enterprise Cloud certified up for FedRAMP, FISMA approval. We're IL-2 civilian agency certified. So we're one of maybe 30 service providers out there in that regard. We'll be one of a handful that'll be DoD certified hopefully by the end of this year at IL-4 off-prem. So those are the two sort of heritage of VirtuaStream platforms, what we brought into the acquisition. What we announced yesterday was the VirtuaStream Storage Cloud, which was really a project that was incubated inside of EMC for a single customer. For any of those EMCers, you'd know of it as Rubicon. And it was a multi-exabyte, hyperscale type of platform. And we brought it over into VirtuaStream, standing it now and connecting it to the various compute components of our Enterprise Cloud in support of common compute across all platforms. And ultimately hardened it. We wrote a layer of software similar to what we did with VirtuaStream, that layer of software of extreme, our CMP largely resides atop VMware's vSphere technology. We've written a layer of software that largely resides atop ECS, which is EMC's Object Scale Out Appliance. And we've hardened the data durability, 13.9s, standard markets about 11.9s, continuous read-write over full-site failure. So we'll be able to offer things like an infrequent access price for a, or offer a premium service or resiliency around an infrequent access price. You have standard pricing, infrequent access, pricing in that industry. And the big thing is we're tethered to EMC on-premises storage and data protection devices. So that's, I mean, it's an obvious strategy, right? EMC is dealing with the emergence of the public cloud, data moving to S3, Azure, and other clouds, other public clouds. So if our customers want a strategy of utilizing a public cloud for, you know, tiering of policy-based tiering, cold and frozen data, archiving of primary storage, long-term retention of backups, that type of thing, we'll have automated connectors. And you guys know how that works. It's just more efficient staying in the same software plane. And so all of that's available now. We're rolling, you know, we're starting with VMAX and the EMC Data Protection Suite and Isilon. We'll roll out, you know, Unity and VNX and Data Domain and those products throughout Q3.  Now that you're going to get in the, you know, the different side of the public cloud market, people are going to want to know what that means. Amazon tells you where their points of presence are. What does expansive scaling look like? Where, you know, where are the foot prints? Sure, sure. So the enterprise, the physical cloud node footprint for our enterprise cloud and for our storage cloud is pretty similar. In fact, we're in a lot of the same facilities. We obviously work to try and make that as efficient as we possibly could. In North America, we have full coverage over multiple zones. In Europe, we're in the UK, Netherlands, France and Germany, we're just lighting up France and Germany literally this quarter. And we'll expand in Asia pack in the second half of the year. So, you know, pretty strong presence through Western Europe. My next focus market's going to be Japan and Asia pack. I actually think for what we do, Japan could be a second or third largest market for us. Yeah. The other question that didn't, I don't know if it got the answer, what does pricing look like for the storage cloud? Yeah, so we'll announce that on May 10th when it GAs. But it's quite interesting, we'll be priced, you know, so if you take like a 50 terabyte standard volume, we'll be priced right at where, you know, Google's a little bit lower right now on unit price. Azure is a little bit higher to equal S3. AWS doesn't have an infrequent access premium service. You know, Azure has a premium service for infrequent. But the data points are well known, they're well published. So we'll price right at where S3 will be priced from a unit price perspective. However, we're going to include 20% transaction in egress volume within that price. So one of the tensions in this space is sort of the toll booth that exists on data coming in and out, right? And we're going to include 20% of that volume as just packaged with that unit price. So the unit price will look similar, but if you look at the absolute value cost curve, and this will be each client's sort of own cost curve, they'll have to determine how much they're going to access this data and where on that price curve we can be advantageous. But our price curve should be lower in most cases. We put a lot of thought into that. We figured just pricing unit price at the same transaction cost philosophy would underserve what we're doing. And so we have something out there that's quite unique from that standpoint. We'll see how it works. Right, right. The other thing that got announced was Pivotal Cloud Foundry Umbridge. Where does that fit in the portfolio? Is it on the enterprise side? Is it on the storage cloud side? It's on the enterprise side. It's actually, we have a Mirantis OpenStack compute system that supports the storage cloud, right? So from an underlying compute perspective, we'll connect PCF to our enterprise cloud, which would be the vSphere API, and then we'll use an OpenStack API for more self-service oriented stuff versus managed SLA stuff. And it's interesting, we have a lot of intersection with Pivotal. Pivotal's done a phenomenal job of penetrating large enterprise to sell platforms, develop cloud native apps. So as we looked at this and prioritized our roadmap, we had a lot of intersecting customers, right? You know, where we're both in there doing stuff. You saw, you guys saw Coca-Cola on stages, those kind of brands, you know, it's kind of the big stuff. We've been able to kind of gain credibility, improve our platform there in that genre of customer, and they have as well. And it's interesting, you know, when these customers look to develop cloud native apps, they're looking for a more robust supporting infrastructure. A lot of them will actually implement PCF in their own data centers, right? And so what we're doing is more emulating that on-prem experience with our enterprise cloud, but allowing them to not provision hardware themselves. So same sort of value position you had with the SAP. Yeah, and so we're not, you know, one of the things that we're very, very careful to do is not attempt to present ourselves with something or not, right? 2009 when we started, everybody was out there chasing, you know, that distributed general IaaS utility, distributed app in general is IaaS utility. That worked out really, really well for like two people, and it worked out horribly for just about everybody else. We chose not to go down that path. I felt it would be venture capital suicide. In cloud native, again, we'll start to expand. We can run these types of apps. We're just optimized for our core use case, IO intensive, more scale up, performant type of requirements. So our path here for cloud native was first and foremost, getting a platform to develop cloud native apps and support that with the infrastructure. And then how we expand our use case, we're just going to do that really carefully in terms of how we deploy and run these apps. So, Rodney, last year, there was a plan to put the Virtus.treme and the vCloud Air vCloud network on that single roof, so, of course, there was a little bit of pushback and that came undone. So can you give us kind of the compare, contrast, adoption of Virtus.treme, you know, how's the relationship with kind of vCloud Air and the vCloud Air network?  I would tell you, it was a very well-intended, a very well-founded strategy. When we were being acquired by EMC, we were very well aware of this.  And so, VMware was looking to participate in this endeavor. So when we were just the speed of the deal, we felt it was necessary for EMC to follow through with a full acquisition. And then we set about structuring this joint venture where VMware and EMC would own us together. That would have meant we would have taken vCloud Air and consolidated it with our Virtus.treme IaaS. This just, it just makes sense on the most basic level. You're consolidating your as-a-service in one place and we were going to move our software portfolio to VMware. This is all public information, it's well-known. VMware's top enterprise software company, they're going to sell a lot more software than we would have, right? You know, in that original construct. And, you know, all of this was fundamentally done predate Dell deal economics. You know, the Dell deal came along as a larger deal and it's the end of the day. It just fundamentally structurally and from an economic perspective made sense to not do it. We had relatively well integrated. We had to unwind that. And, you know, as it relates to how we collaborate with VMware, we're very close to VMware still. You know, we run 90 plus percent of our workloads on underlying vSphere VMware technology. We're integrating NSX. That's one of the other roadmap items. We will use NSX for network automation here by the second half of this year. So we maintain a very close relationship. VMware has, still has VCloud Air in its portfolio. They've kind of, you know, they publicly stated that they're kind of going to take a very focused use case around VCloud Air and we're kind of letting them do their thing. Quite frankly, Stu, you know, we didn't compete. VMware and VCloud Air didn't often compete. Really, very, very, very rarely. And that was one of the things that, you know, the combination was largely accretive in terms of customers and use case and things of that nature. Yeah. So obviously the original VirtuaStream use case was enterprises trusted you to run there. You were running their operations. You know, there are still going to be companies who say, I understand that concept. I like the concept, but I have to have data local, you know, on-prem or whatever reason. You know, we're seeing Oracle get in that space. We're seeing IBM with IBM local. I keep hearing around the floor that you inherited this managed service. When are we going to hear more about what that's capable of? For customers who say, you know, I can't do operations, it's hard. Chad talked about how hard it is on the keynote. When will we learn more about that? That's a great point. You know, we tend to talk a lot about the technology, not the service that's running the technology. We did. We brought in 1,200 people or so into Virtstream from EMC's managed services group. And these were professionals that largely managed on-premises EMC installations. And we have brought that in. We've integrated our managed services team at Virtstream. So the Heritage Virtstream, we had a managed services group that largely manages the apps and these three-tier application architecture landscapes that reside on our cloud. So we've brought that in. EMC had great people, a lot of maturity around methodologies, tools, service desk, ticket processing, all the things that you a lot of times lack as a young company is one coming up. So we've taken great advantage of that and we've gotten that hardened. And the point, you know this, Brian, our point of view has always been we never got involved in those religious debates between public cloud and private cloud. We always felt that was a bit silly. Your use case, your consumption is going to need to be which is simply driven by where the economics dictate what regulatory requirements are there, what latency requirements are there. You know, it's just like, I just get a kick out of, you know, you listen to the purists talk about if an app's not architected, you use a public cloud and you need to rewrite the app. I've seen that very rarely actually occur. You know, at least in the stuff that's running the live ammo production workloads and such. And so, you know, we need to just be prepared to support the app wherever it's running. And that's our objective.  All right, so Rodney, I can't let you go without asking you the big question of course. Heat, still alive, LeBron still alive.  Well, the heat will clearly win the finals this year. You know, I don't think Olin stands much of a chance. I say that tongue in cheek. We had a couple of great years with LeBron down in Miami. You know, when he left Cleveland, they were burning effigies of him, you know, there and stuff. And when he left Miami, it wasn't really like that. You know, everybody was kind of appreciative. They kind of respected his reason for going back to Cleveland. I did, you know, we're sorry to see him leave. Dwayne Wade has had a total resurgence. I'm not sure what happened there, but he's playing awesome, man. So, you know, we've got a good young team, you know, Whiteside and Richards, you know, those guys are pretty, pretty, pretty good looking team at this stage of the game. So, we'll see how far they can go. They won against Toronto. My schedule at this thing is, you know, starts at 7 a.m. ends at midnight. So, I couldn't even watch the game, which is like sacrilege for me, man. I'm hopeful. And yeah, he will win it. You heard it right here. He won the NBA championship. All right, well, Rodney Rogers, really appreciate it. I know everybody's going wall-to-wall here at EMC World. Hope to catch up with you much more soon. We'll be back with lots more coverage here from EMC World 2016. You're watching theCUBE. Looking back at...