search for: 136053

...d a patch some time ago to modify the target triple code to enable this, but after a bit of discussion there didn't seem to be a consensus for accepting this proposal. If you want to try it out, the patch can be found here: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20120130/136053.html I believe you can also find the related discussions from that post. We've had success using this patch to generate ELF on Windows. I don't know if any progress has been made toward a more generally acceptable solution. -Andy -----Original Message----- From: llvmdev-bounces at cs....

...neral way > to specify a non-default object format for any platform rather than a > Windows/ELF-specific extension.**** > > **** > > The original discussion can be found here:**** > > **** > > > http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20120130/136053.html > **** > > **** > > Unfortunately, I don't believe a consensus was ever reached as to what the > correct way to implement this would be. I'd like to re-open that > discussion now so that we can find a solution that would be generally > accepted for inclusion i...

...me ago to modify the target triple code to enable this, but after a bit of discussion there didn't seem to be a consensus for accepting this proposal. > > If you want to try it out, the patch can be found here: > > http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20120130/136053.html > > I believe you can also find the related discussions from that post. We've had success using this patch to generate ELF on Windows. I don't know if any progress has been made toward a more generally acceptable solution. > > -Andy > > > -----Original Message---...

Just wondering if you don't respond to donations or don't get notified?

...:XX:XX:XX:XX inet addr:aaa.bbb.ccc.26 Bcast:aaa.bbb.ccc.255 Mask:255.255.255.0 inet6 addr: xxxx::xxx:xxx:xxxx:xxxx/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:223374 errors:0 dropped:0 overruns:0 frame:0 TX packets:136053 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:22056304 (21.0 MiB) TX bytes:20211609 (19.2 MiB) eth0:180 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX inet addr:aaa.bbb.ccc.180 Bcast:aaa.bbb.ccc.255 Mask:255.255.255.0 UP...

...re seemed to be a general feeling that it would be preferable to have a general way to specify a non-default object format for any platform rather than a Windows/ELF-specific extension. The original discussion can be found here: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20120130/136053.html Unfortunately, I don't believe a consensus was ever reached as to what the correct way to implement this would be. I'd like to re-open that discussion now so that we can find a solution that would be generally accepted for inclusion in LLVM. We can, of course, discuss any and all of...

Hi Verena, Windows + MachO is likely to run into lots of problems once you start passing in non-trivial code. The relocation model is very tied to Darwin. I believe some folks doing JIT on Windows have had some success w/ ELF. Hopefully someone more familiar with the specifics of that will chime in. -Jim On Jun 29, 2012, at 8:58 AM, Verena Beckham <verena at codeplay.com> wrote: >

...re seemed to be a general feeling that it would be preferable to have a general way to specify a non-default object format for any platform rather than a Windows/ELF-specific extension. The original discussion can be found here: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20120130/136053.html Unfortunately, I don't believe a consensus was ever reached as to what the correct way to implement this would be. I'd like to re-open that discussion now so that we can find a solution that would be generally accepted for inclusion in LLVM. We can, of course, discuss any and all of...

Hi, In X86MachObjectWriter::RecordX86Relocation I found the comment if (Target.isAbsolute()) { // constant // SymbolNum of 0 indicates the absolute section. // // FIXME: Currently, these are never generated (see code below). I cannot // find a case where they are actually emitted. Type = macho::RIT_Vanilla; } Is the FIXME still true? I've got some code that

...al feeling that it would be preferable to have a general way to specify a non-default object format for any platform rather than a Windows/ELF-specific extension. > > The original discussion can be found here: > > http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20120130/136053.html > > Unfortunately, I don't believe a consensus was ever reached as to what the correct way to implement this would be. I'd like to re-open that discussion now so that we can find a solution that would be generally accepted for inclusion in LLVM. > > We can, of course,...

...re seemed to be a general feeling that it would be preferable to have a general way to specify a non-default object format for any platform rather than a Windows/ELF-specific extension. The original discussion can be found here: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20120130/136053.html Unfortunately, I don't believe a consensus was ever reached as to what the correct way to implement this would be. I'd like to re-open that discussion now so that we can find a solution that would be generally accepted for inclusion in LLVM. I'm using this patch mentioned and it...