search for: appent

...cessary changes and these are mostly constrained to the files: >> >> X86IntelAsmPrinter.[h|cpp] >> >> X86TargetAsmInfo.[h|cpp] > >Sounds good; did you mean to attach a patch? It'll be easier to >discuss with that. (The output of "svn diff" is fine.) Appently the GAS Intel backend has flaws and does not work correctly anyway so the X86IntelAsm backend is designed only to target MASM anyway. Aaron

On Tuesday 16 June 2009 09:48, Aaron Gray wrote: > Appently the GAS Intel backend has flaws and does not work correctly anyway > so the X86IntelAsm backend is designed only to target MASM anyway. gas Intel syntax is indeed broken in LLVM. I'd love to make it work but my work has not (yet) allocated time for that. Maybe I can hack LLVM on the wee...

On Jun 16, 2009, at 3:12 PM, David Greene wrote: > On Tuesday 16 June 2009 09:48, Aaron Gray wrote: > >> Appently the GAS Intel backend has flaws and does not work >> correctly anyway >> so the X86IntelAsm backend is designed only to target MASM anyway. > > gas Intel syntax is indeed broken in LLVM. I'd love to make it work > but > my work has not (yet) allocated time for tha...

Hello, I have tried to apply the raid-2.2.19-A1 patch from http://www.redhat.com/~mingo and ext3 0.0.7a, but it conflicts with the include/fs.h. The conflict is about the bit-numbering: ext3 uses several new files, and raid also wants to use one new flag. Can I simply appent the new value to the list of "BL_*" variables (BL_LowPrio wants to be 8, but the first free slot is 16). dLux -- ..all in all it's just another rule in the firewall. /Ping Flood/

> On Tuesday 16 June 2009 09:48, Aaron Gray wrote: > >> Appently the GAS Intel backend has flaws and does not work correctly >> anyway >> so the X86IntelAsm backend is designed only to target MASM anyway. > > gas Intel syntax is indeed broken in LLVM. I'd love to make it work but > my work has not (yet) allocated time for that. Mayb...

Using ldap as my sam backend and Samba 3.0.0-2, I'm showing that samba stops parsing a RID when it encounters a letter. For example, I have an accounting group with gid 2771 and therefore rid ad3. When I list the groups in the samba domain, however, I get this listing: Domain Admins (DOMAINSID-512) -> Domain Admins Domain Users (DOMAINSID-513) -> Domain Users Domain Guests

On Mon, Jun 15, 2009 at 5:49 PM, Gaster, Benedict<Benedict.Gaster at amd.com> wrote: > I would like to use the LLVM x86 code generator to emit Intel syntax that is > compatible with Microsoft’s MASM 9.x. Taking the TOT LLVM, from last week, I > have found a number of changes that are required to make this work, most of > which are straight forward but a couple I wanted to check

I would like to use the LLVM x86 code generator to emit Intel syntax that is compatible with Microsoft's MASM 9.x. Taking the TOT LLVM, from last week, I have found a number of changes that are required to make this work, most of which are straight forward but a couple I wanted to check with the group to see what people thought was the best thing to do. In particular, I have made all necessary