search for: fungibl

I asked about this in IRC ~2.5 hours ago: <srnb> I'm trying to write an LLVM backend for the WDC 65816 (for usage in compiling SNES code) but I have very little experience with how C++ works and LLVM's CMakeLists. I'm trying to follow the guide but I don't know how to check if the project builds after my changes or how to test a small amount of C with it once I get it

...tmp/test2'':* * ensure => directory,* * mode => 0644,* * }* * * * file {''/tmp/test3'':* * ensure => link,* * target => ''/tmp/test1'',* * }* * * * notify {"I''m notifying you.":} # Whitespace is fungible, remember.* * notify {"So am I!":}* *warning: Could not retrieve fact fqdn* Any one know why? Regards -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, sen...

...message at the bottom of these emails. I looked through settings but I don't know how to get rid of it. July 10, 2019 1:29 PM, "Tim Northover" <t.p.northover at gmail.com> wrote: > As I recall the big one is that LLVM isn't well adapted to instruction > sets without fungible registers. What does this mean exactly? How does the WDC 65816 not have fungible registers, while other processors do? > One idea is to use some of bank 0 as > a source of registers, maybe with a custom pass to promote things to > real registers where possible after the fact. How would...

...te my MipsSubtargetInfo object whenever it or a derived reference of it is available. I have a reference of SubtargetInfo in <target>ELFObjectWriter in my current patch. I am open to better suggestions as long as it solves the basic issue and allows me to mark up ELF header information with fungible target specific information without affecting other targets going forward. Cheers, Jack ________________________________________ From: Rafael Espíndola [rafael.espindola at gmail.com] Sent: Saturday, December 08, 2012 10:42 AM To: Carter, Jack Cc: List Subject: Re: [LLVMdev] [MC] [llvm-mc] Get...

...ctWriter in my current patch. I don't see a definition of a MipsSubtargetInfo class in the tree. Do you mean MipsSubtarget as defined in MipsSubtarget.h? -Jim > > I am open to better suggestions as long as it solves the basic issue and allows me to mark up ELF header information with fungible target specific information without affecting other targets going forward. > > Cheers, > > Jack > > ________________________________________ > From: Rafael Espíndola [rafael.espindola at gmail.com] > Sent: Saturday, December 08, 2012 10:42 AM > To: Carter, Jack > C...

...jectWriter in my current patch. I don't see a definition of a MipsSubtargetInfo class in the tree. Do you mean MipsSubtarget as defined in MipsSubtarget.h? -Jim > > I am open to better suggestions as long as it solves the basic issue and allows me to mark up ELF header information with fungible target specific information without affecting other targets going forward. > > Cheers, > > Jack > > ________________________________________ > From: Rafael Espíndola [rafael.espindola at gmail.com] > Sent: Saturday, December 08, 2012 10:42 AM > To: Carter, Jack > Cc:...

On 7 December 2012 18:57, Carter, Jack <jcarter at mips.com> wrote: > Hi Rafael, > > There are a lot of flags. Here are the ones you ask about: > > -KPIC, -call_shared generate SVR4 position independent code > -call_nonpic generate non-PIC code that can operate with DSOs > -mvxworks-pic generate VxWorks position independent code > -non_shared

...jectWriter in my current patch. I don't see a definition of a MipsSubtargetInfo class in the tree. Do you mean MipsSubtarget as defined in MipsSubtarget.h? -Jim > > I am open to better suggestions as long as it solves the basic issue and allows me to mark up ELF header information with fungible target specific information without affecting other targets going forward. > > Cheers, > > Jack > > ________________________________________ > From: Rafael Espíndola [rafael.espindola at gmail.com] > Sent: Saturday, December 08, 2012 10:42 AM > To: Carter, Jack > Cc:...

Hi Rafael, There are a lot of flags. Here are the ones you ask about: -KPIC, -call_shared generate SVR4 position independent code -call_nonpic generate non-PIC code that can operate with DSOs -mvxworks-pic generate VxWorks position independent code -non_shared do not generate code that can operate with DSOs -xgot assume a 32 bit GOT Just to make things fun, the SGI notion of cpic (call pic)

https://bugs.freedesktop.org/show_bug.cgi?id=109952 Bug ID: 109952 Summary: nv106 nv108 confusion Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at