search for: nstruct

...^G^C^Y^A^O^@^G^@^G^C^Y^B^O^@^G^@^G������"^@^@^@^@������"^@^@^@^@������^B^Q^@^@^@����^G^F^@^@]^Q^P^@^K<8c>^P^Hb^Q^A^A ^L ^@p^R^B^A^A������p^R^B^A^B������p^R��r^U^A^A^E^G^@^@��^H^@^@^@^A^A^B^Gtmp.1.i^C^G^B^Etmp.0^D^Gtmp.0.i^C^Etmp.2^C^L^L__main.entry^A endif.0.i^@^Eentry��$^M^@^@^B^Y^Nstruct..TorRec^Y^Mstruct.TorRecB^O^A^F.str_2^B^F.str_3^A^R^A^Fprintf^A^U^A^Dexit^A^W^A^Dmain^A^M^A^F.str_1^A^Q^A^OInitialized.0__������ ------------------------------------------------------------------------------- I generated it like this: $llvmgcc prog.c -o prog Thanks Tanu Chris Lattner <sa...

My 2 cents: get rid of LLVM_UNUSED_RESULT, and move to LLVM_NODISCARD. For compilers that support it, it should be a strict superset of features and functionality. The standard feature was written directly based on the clang warn_unused_result stuff. I would just migrate us onto the spelling and usage pattern that got standardized. All we have to lose are warnings from compilers other than Clang

On Tue, 30 Nov 2004, Tanu Sharma wrote: > I have trouble using the llvm tools.Some of the errors are : > > $ llvm-dis prog.bc > $ llvm-dis: Invalid Top Level Block Length! Type:1, Size:456 (Vers=0, Pos=12) Can you explain how you generated this bytecode file? It looks corrupted or something. Also, can you send the actual bytecode file itself? Thanks! -Chris >

I last posted this back in April to critical acclaim (AKA near total silence). I''m not sure who looks after tools/include/xen-foreign. I had thought it was Jan but I think I was confused and was thinking of the semi-related xen/include/compat stuff. IOW I think nobody felt "responsible". Unless there''s any objection lets just treat this as coming under tools. The