similar to: [LLVMdev] Questions on ARMInstrInfo.td and MC/ARM/ELF

Displaying 20 results from an estimated 1100 matches similar to: "[LLVMdev] Questions on ARMInstrInfo.td and MC/ARM/ELF"

2010 Sep 29
0
[LLVMdev] Questions on ARMInstrInfo.td and MC/ARM/ELF
On Sep 29, 2010, at 3:09 PM, Jason Kim wrote: > Hi Everyone, > > I am trying to decide on a MC'ized reorg of ARMAsmPrinter for MC/ELF, > and had some questions. > > Currently, it defines quite a few methods like printAddrMode4Operand > (linked to ARMInstrInfo.td) that currently assume raw text support in > the OutStreamer. Are these methods still supposed to be
2010 Sep 29
2
[LLVMdev] Questions on ARMInstrInfo.td and MC/ARM/ELF
On Wed, Sep 29, 2010 at 4:00 PM, Jim Grosbach <grosbach at apple.com> wrote: > > On Sep 29, 2010, at 3:58 PM, Anton Korobeynikov wrote: > >> Hi Jim, >> >>> Since this is by definition only for .s file emission, why is this clearly wrong? Perhaps it is, but it's not obvious to me why. >> Attributes should be emitted into object file as well... > >
2010 Sep 29
2
[LLVMdev] Questions on ARMInstrInfo.td and MC/ARM/ELF
Hi Jim, > Since this is by definition only for .s file emission, why is this clearly wrong? Perhaps it is, but it's not obvious to me why. Attributes should be emitted into object file as well... -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University
2010 Sep 29
0
[LLVMdev] Questions on ARMInstrInfo.td and MC/ARM/ELF
On Sep 29, 2010, at 3:58 PM, Anton Korobeynikov wrote: > Hi Jim, > >> Since this is by definition only for .s file emission, why is this clearly wrong? Perhaps it is, but it's not obvious to me why. > Attributes should be emitted into object file as well... Yes, but surely not by a function explicitly indicated to be for assembly files. I would expect there to be an
2010 Sep 29
0
[LLVMdev] Questions on ARMInstrInfo.td and MC/ARM/ELF
On Sep 29, 2010, at 4:27 PM, Jason Kim wrote: >> Yes, but surely not by a function explicitly indicated to be for assembly files. I would expect there to be an equivalent function to do what needs done for object files. Perhaps there isn't one (yet) and that's what's leading to the confusion? > > LOL :-) Yes, maybe that's it. Included is a patch w comments that >
2010 Oct 21
5
[LLVMdev] [llvm-commits] Fwd: Proof of concept patch for unifying the .s/ELF emission of .ARM.attributes
> Also what is the preferred method for MC way of setting out subsection > sizes after the fact? I am guessing I need to use an MCFixup? > How do I get an MCExpr to evaluate a method for the subsection size? > Is there an equivalent use in the places using MCFixup? > Do I need to add a new subclass to MCExpr for doing this? > > JimG, can you please comment on the MachO
2011 Dec 21
0
[LLVMdev] Typos in ARMInstrInfo.td ?
Thanks. Fixed with r147032. Evan On Dec 16, 2011, at 1:50 AM, George Russell wrote: > Hi, > > I think there are a set of typos in the ATOMIC_LOAD_UMIN_I* and > ATOMIC_LOAD_UMAX_I* > pseudo-instructions . > > Specifically, > > def ATOMIC_LOAD_MIN_I32 : PseudoInst< > (outs GPR:$dst), (ins GPR:$ptr, GPR:$val), NoItinerary, >
2011 Dec 21
1
[LLVMdev] Typos in ARMInstrInfo.td ?
Hi Evan, The problem repeats with the i8 and i16 variants, as well. Cheers, George On 21/12/2011 04:07, Evan Cheng wrote: > Thanks. Fixed with r147032. > > Evan > > On Dec 16, 2011, at 1:50 AM, George Russell wrote: > >> Hi, >> >> I think there are a set of typos in the ATOMIC_LOAD_UMIN_I* and >> ATOMIC_LOAD_UMAX_I* >> pseudo-instructions .
2011 Dec 16
2
[LLVMdev] Typos in ARMInstrInfo.td ?
Hi, I think there are a set of typos in the ATOMIC_LOAD_UMIN_I* and ATOMIC_LOAD_UMAX_I* pseudo-instructions . Specifically, def ATOMIC_LOAD_MIN_I32 : PseudoInst< (outs GPR:$dst), (ins GPR:$ptr, GPR:$val), NoItinerary, [(set GPR:$dst, (atomic_load_min_32 GPR:$ptr, GPR:$val))]>; and def ATOMIC_LOAD_UMIN_I32 : PseudoInst< (outs
2011 Feb 25
0
[LLVMdev] ARM ELF target and the use of VFP/NEON instructions
On Fri, Feb 25, 2011 at 12:16 PM, Siarhei Siamashka <siarhei.siamashka at gmail.com> wrote: > On Thursday 03 February 2011 14:14:28 Renato Golin wrote: >> On 3 February 2011 10:25, Siarhei Siamashka <siarhei.siamashka at gmail.com> > wrote: >> > I have submitted a bug some time ago to LLVM bugtracker: >> > http://llvm.org/bugs/show_bug.cgi?id=8931 >>
2011 Feb 25
2
[LLVMdev] ARM ELF target and the use of VFP/NEON instructions
On Thursday 03 February 2011 14:14:28 Renato Golin wrote: > On 3 February 2011 10:25, Siarhei Siamashka <siarhei.siamashka at gmail.com> wrote: > > I have submitted a bug some time ago to LLVM bugtracker: > > http://llvm.org/bugs/show_bug.cgi?id=8931 > > Hi Siarhei, > > This is a really silly bug with a simple fix. > > We have a similar patch here
2011 Jun 17
2
[LLVMdev] Simple clang + llc crash on Windows 7
Hello, I'm eager to get to know Clang+LLVM but I'm having some problems generating debug information that force llc.exe to crash. I'm running from the command-line on Windows 7 with clang+llvm versions 2.9 downloaded from the website. The input file is main.c:      void mainCRTStartup()      {      } This is compiled to intermediate with debug symbols using:      clang -g -O0 -c
2010 Oct 21
3
[LLVMdev] [llvm-commits] Fwd: Proof of concept patch for unifying the .s/ELF emission of .ARM.attributes
> Hmm, I wish we had this discussion way earlier.. > > How would I emit things in different subsections? I can do a high > level switch to .ARM.attributes, and if I were emitting one blob from > begin to end, using the higher level interface would be preferable, > but it contains additional subsections - which are naturally > represented by MCDataFragments - Is there an MC
2010 Oct 21
0
[LLVMdev] [llvm-commits] Fwd: Proof of concept patch for unifying the .s/ELF emission of .ARM.attributes
On Thu, Oct 21, 2010 at 7:50 AM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: >> Hmm, I wish we had this discussion way earlier.. >> >> How would I emit things in different subsections? I can do a high >> level switch to .ARM.attributes, and if I were emitting one blob from >> begin to end, using the higher level interface would be preferable,
2010 Oct 21
2
[LLVMdev] Fwd: [llvm-commits] Proof of concept patch for unifying the .s/ELF emission of .ARM.attributes
On Wed, Oct 20, 2010 at 2:56 PM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: >> Gosh, this is taking a while :-) >> Is there anything else I missed? > > Another one I noticed. Instead of > >      SmallString<32> *FC = &currFileFragment.getContents(); >      (*FC) += static_cast<char>(attr); >      (*FC) += static_cast<char>(0xFF
2011 Jun 17
0
[LLVMdev] Simple clang + llc crash on Windows 7
On Fri, Jun 17, 2011 at 11:07 AM, Don Williamson <don.williamson at yahoo.com> wrote: > And I get a crash with the error message: > >      EmitRawText called on an MCStreamer that doesn't support it,  something must not be fully mc'ized > > I understand from the 2.9 release notes that filetype=obj is currently experimentalbut the above is lifted from the visual studio
2011 Jun 17
2
[LLVMdev] Simple clang + llc crash on Windows 7
OK, thanks - that's a real shame. ----- Original Message ----- From: Eli Friedman <eli.friedman at gmail.com> To: Don Williamson <don.williamson at yahoo.com> Cc: "llvmdev at cs.uiuc.edu" <llvmdev at cs.uiuc.edu> Sent: Friday, June 17, 2011 7:27 PM Subject: Re: [LLVMdev] Simple clang + llc crash on Windows 7 On Fri, Jun 17, 2011 at 11:07 AM, Don Williamson
2010 Oct 22
1
[LLVMdev] Fwd: [llvm-commits] Fwd: Proof of concept patch for unifying the .s/ELF emission of .ARM.attributes
---------- Forwarded message ---------- From: Jason Kim <jasonwkim at google.com> Date: Fri, Oct 22, 2010 at 12:59 PM Subject: Re: [llvm-commits] Fwd: Proof of concept patch for unifying the .s/ELF emission of .ARM.attributes To: Rafael Espíndola <rafael.espindola at gmail.com> On Fri, Oct 22, 2010 at 12:51 PM, Jason Kim <jasonwkim at google.com> wrote: > On Thu, Oct 21,
2014 Sep 30
2
[LLVMdev] Custom pass that runs before EmitStartOfAsmFile()?
Hi all, I'm trying to write a custom module-level pass that runs before AsmPrinter::EmitStartOfAsmFile(), since I'd like to have some processed information available once entering this function. Looking through "Writing an LLVM pass" documentation, it's not clear to me if this is possible. I've also tried putting the pass in different orders (addPreISel, addIRPasses,
2011 Jul 27
2
[LLVMdev] llvm-mc build failure
Dear llvm, Recently (approximately a week ago) Clang and LLVM started to failed at building. Assuming it was my incompetence, I cleared everything and started witha fresh checkout (not that I changed it though). I am on Ubuntu 10.04 LTS 64-Bit. And I configure and compile with CMake. The error message I get at approximatley 66% is as follows: Linking CXX executable ../../bin/llvm-mc