<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:st="" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"
xmlns:ns0="http://schemas.microsoft.com/office/2004/12/omml">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--a:link
{mso-style-priority:99;}
span.MSOHYPERLINK
{mso-style-priority:99;}
a:visited
{mso-style-priority:99;}
span.MSOHYPERLINKFOLLOWED
{mso-style-priority:99;}
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:Arial;
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:Calibri;
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:595.3pt 841.9pt;
margin:2.0cm 42.5pt 2.0cm 3.0cm;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=RU link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>Hi Andrew,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>Thank you for the
detailed explanation.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>I have carefully studied
your patch and DyldELFObject.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>A gdb support is very
important and it's actually a big step for MCJIT. I like your patch, its
loadObject() looks faster than my. But I see one big conceptual problem.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>The RuntimeDyLd was
developed as a linker, which is able to prepare data for running on another
platform. The RuntimeDyldMachO largely implements it.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>In the RuntimeDyldELF you
went the other way. Now it is very far from remote execution. And even if the
object file will be emitted with RTDyldMemoryManager, it is not a good idea:
(1) remote execution doesn't need many parts of object file, such as debugging
information, headers, section table and etc, (2) some sections is code and must
has execution permit, some sections is data without execution permit, so the
best way is use a different methods for emits different type of sections.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>If your patch will be committed,
we obtain a RuntimeDyldMachO and RuntimeDyldELF, which different principles and
a different results. And most likely, for ELF will never be fully realization
for remote execution.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>I think another ways will
be better, just for instance, two possible solutions:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>1. Always emits the
sections required to execution with a RTDyldMemoryManager. Resolve relocation
in these sections. And if the isDebugging flag is set, then in addition,
DyldELFObject::rebaseObject make his job, except that for the sections stored
by the RTDyldMemoryManager write the correct address.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>2. Check the debug flag
at first, before load object file. If it set, just use your realization of
loadObject, otherwise - use normal way with RTDyldMemoryManager.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>Both alternatives have
their shortcomings, perhaps you find another solution. Also, I would be glad to
hear that Jim thinks about it.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>Now I trying to merge
your patch with my.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>Regards,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>Danil<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> Kaylor, Andrew
[mailto:andrew.kaylor@intel.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, February 09, 2012
4:56 AM<br>
<b><span style='font-weight:bold'>To:</span></b> Danil Malyshev; <st1:PersonName
w:st="on">llvm-commits@cs.uiuc.edu</st1:PersonName><br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: RuntimeDyLd new
features</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Calibri><span lang=EN-US
style='font-size:11.0pt;font-family:Calibri;color:black'>Hi Danil,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Calibri><span lang=EN-US
style='font-size:11.0pt;font-family:Calibri;color:black'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Calibri><span lang=EN-US
style='font-size:11.0pt;font-family:Calibri;color:black'>Thanks for your
efforts in this area. As Eli Bendersky mentioned, we have a patch out for
review in this area also. I'm hopeful that we can find a convergence between
our code, your code and the code that Jim Grosbach has put in place.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Calibri><span lang=EN-US
style='font-size:11.0pt;font-family:Calibri;color:black'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Calibri><span lang=EN-US
style='font-size:11.0pt;font-family:Calibri;color:black'>Unfortunately, we have
been submitting our code in small chunks for ease of review and to keep things
stable, and it may not be obvious from what we've put out for review what our
intentions were or our intended solutions to the problems that were left
open. I'd like to take this opportunity to discuss the direction we we're
heading and see how it might align with what you and Jim have done.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Calibri><span lang=EN-US
style='font-size:11.0pt;font-family:Calibri;color:black'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Calibri><span lang=EN-US
style='font-size:11.0pt;font-family:Calibri;color:black'>Let me first explain
what we have done, and then I'll offer specific comments on your code and
possible next steps.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Calibri><span lang=EN-US
style='font-size:11.0pt;font-family:Calibri;color:black'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Calibri><span lang=EN-US
style='font-size:11.0pt;font-family:Calibri;color:black'>We have had two
primary goals: (1) to get MCJIT generated code to work correctly on Intel
architecture and help pave the way for other implementations and (2) enable
source-level debugging of JITed code with GDB. This second goal seems to
be dropping from view, but it places a few constraints on the eventual
implementation. We've had GDB integration working, BTW.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Calibri><span lang=EN-US
style='font-size:11.0pt;font-family:Calibri;color:black'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Calibri><span lang=EN-US
style='font-size:11.0pt;font-family:Calibri;color:black'>In order to get GDB to
handle JITed code, we need to register an ELF object image through an interface
GDB defines. As you might expect, GDB has some peculiar expectations for
what this ELF object image should look like. In particular, we need to
set a flag in the ELF header and update the sh_addr members in the section
headers to reflect the address where the section contents reside in memory.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Calibri><span lang=EN-US
style='font-size:11.0pt;font-family:Calibri;color:black'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Calibri><span lang=EN-US
style='font-size:11.0pt;font-family:Calibri;color:black'>Our most recent patch
(<a
href="http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20120130/135997.html">http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20120130/135997.html</a>,
not yet committed) begins by copying the entire ELF image emitted by the MC
code generator into an executable buffer. This was intended as a
temporary step toward our eventual solution. It enabled us to perform
relocations in-place on the object and execute functions in place (thus
eliminating an extra copy that was previously being done). We were in the
process of implementing a smarter section-based approach, but Jim Grosbach was
implementing a similar approach in parallel and our submission ended up
appearing out of step in this regard.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Calibri><span lang=EN-US
style='font-size:11.0pt;font-family:Calibri;color:black'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Calibri><span lang=EN-US
style='font-size:11.0pt;font-family:Calibri;color:black'>So that's our
background. Now, returning to your patch....<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Calibri><span lang=EN-US
style='font-size:11.0pt;font-family:Calibri;color:black'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Calibri><span lang=EN-US
style='font-size:11.0pt;font-family:Calibri;color:black'>I like the idea of
combining as much common code as possible into the RuntimeDyldImpl class.
I'm interested to hear from users of the MachO loader if your implementation
has lost any of the specialization that they need. I think it's a
promising approach. There are some ELF-specific details that we will need
to have incorporated to re-enable GDB integration, but I expect that we'll be
able to find a way to work that in with a few well-placed overloaded function
calls.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Calibri><span lang=EN-US
style='font-size:11.0pt;font-family:Calibri;color:black'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Calibri><span lang=EN-US
style='font-size:11.0pt;font-family:Calibri;color:black'>I have some
reservations about the use of the basic ObjectFile interface, which has some
serious limitations. We've been working toward exposing the ELFObjectFile
template for use in the runtime loading process (as well as other unrelated
uses). It may be that this is something that can be generalized enough to
fit with your approach. My main concern in this regard is that we need to
be able to update specific entries in the ELF image, as described above.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Calibri><span lang=EN-US
style='font-size:11.0pt;font-family:Calibri;color:black'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Calibri><span lang=EN-US
style='font-size:11.0pt;font-family:Calibri;color:black'>A related issue is
that section loading can be refined with some ELF-specific details. Some
sections need to have memory allocated for their contents. Other sections
can be left in place in the originally generated image. There is a good
bit of unnecessary copying going on in the existing implementation, and I'm not
clear to what extent your patch addresses that. Before the object is
loaded, it is copied into a new buffer and then the contents of each section
are copied again as we go. What I'd like is for the runtime loaders to
use the buffer into which the object is originally generated and only make
copies where it is strictly necessary. This isn't necessarily something
you need to do for your work to be acceptable, but I mention it as a likely
next step.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Calibri><span lang=EN-US
style='font-size:11.0pt;font-family:Calibri;color:black'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Calibri><span lang=EN-US
style='font-size:11.0pt;font-family:Calibri;color:black'>Over the next few days
I intend to apply your patch locally and try to merge our work into it.
I'll provide additional feedback as I get a better feel for what you've done.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Calibri><span lang=EN-US
style='font-size:11.0pt;font-family:Calibri;color:black'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Calibri><span lang=EN-US
style='font-size:11.0pt;font-family:Calibri;color:black'>-Andy</span></font><font
size=2 color="#1f497d" face=Calibri><span lang=EN-US style='font-size:11.0pt;
font-family:Calibri;color:#1F497D'><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span lang=EN-US
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><font size=2 face=Tahoma><span lang=EN-US
style='font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</span></font></b><font
size=2 face=Tahoma><span lang=EN-US style='font-size:10.0pt;font-family:Tahoma'>
llvm-commits-bounces@cs.uiuc.edu [mailto:llvm-commits-bounces@cs.uiuc.edu] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Danil Malyshev<br>
<b><span style='font-weight:bold'>Sent:</span></b> Tuesday, February 07, 2012
12:24 PM<br>
<b><span style='font-weight:bold'>To:</span></b> <st1:PersonName w:st="on">llvm-commits@cs.uiuc.edu</st1:PersonName><br>
<b><span style='font-weight:bold'>Subject:</span></b> [llvm-commits]
RuntimeDyLd new features<o:p></o:p></span></font></p>
</div>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span lang=EN-US
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'>Hello everyone,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'>Please review the RuntimeDyLd-01.patch.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'>This patch makes the following changes:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'>1. The main works will made in the RuntimeDyLdImpl
with uses the ObjectFile class. RuntimeDyLdMachO and RuntimeDyLdELF now only
parses relocations and resolve it. This is allows to make improvements of the
RuntimeDyLd more easily. In addition the support for COFF can be easily added.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'>2. Added ARM relocations to RuntimeDyLdELF.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'>3. Added support for stub functions for the ARM,
allowing to do a <st1:City w:st="on"><st1:place w:st="on">long branch</st1:place></st1:City>.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'>4. Added support for external functions that are not
loaded from the object files, but can be loaded from external libraries. Now
MCJIT can correctly execute the code containing the printf, putc, and etc.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'> <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'>5. The sections emitted instead functions, thanks Jim
Grosbach. MemoryManager.startFunctionBody() and MemoryManager.endFunctionBody()
have been removed.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'>6. MCJITMemoryManager.allocateDataSection() and
MCJITMemoryManager. allocateCodeSection() used JMM->allocateSpace() instead
of JMM->allocateCodeSection() and JMM->allocateDataSection(), because I
got an error: "Cannot allocate an allocated block!" with object file
contains more than one code or data sections.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'>7. Fixed ELF::R_X86_64_PC32 relocation for the case
when RealOffset is negative value.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'>8. Added new testing folder: ExecutionEngine/MCJIT
because mcjit tests can be running only for x86 and arm and it's can be
filtered with dg.exp.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'>Tested in Ubuntu x86_64, Ubuntu armv7 and MacOS 64.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'>Thank you,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'>Danil<o:p></o:p></span></font></p>
</div>
</body>
</html>