Displaying 3 results from an estimated 3 matches for "ll_end".
Did you mean:
l_end
2010 May 20
0
[LLVMdev] Win32 COFF Support
...;coff::section *> name_section_map;
Unused typedefs?
5. For the following bit (and a few others in the same function):
+ for (i = Sections.begin(), j = Asm.begin();
+ (i != Sections.end()) && (j != Asm.end());
+ i++, j++) {
http://llvm.org//docs/CodingStandards.html#ll_end
6.
+namespace llvm { MCObjectWriter * createWinCOFFObjectWriter
(raw_ostream & OS); }
If you need a function to be visible across files, use a header;
shortcuts like this make the code more difficult to read.
-Eli
2010 May 20
6
[LLVMdev] Win32 COFF Support
Hi guys,
I have attached my patch to support generating win32 COFF object files. I
would have posted earlier, but my system drive crashed and I had to rebuild
my system; Luckily, my source code was on a secondary drive. I think this
would be a good beginning for ongoing support of the COFF object file format
and was hoping for some feedback as to whether it was commit worthy or what
was needed to
2010 May 20
2
[LLVMdev] Win32 COFF Support
...ntation, will remove.
>
> 5. For the following bit (and a few others in the same function):
> + for (i = Sections.begin(), j = Asm.begin();
> + (i != Sections.end()) && (j != Asm.end());
> + i++, j++) {
>
> http://llvm.org//docs/CodingStandards.html#ll_end
>
>
I will recode those statements.
> 6.
> +namespace llvm { MCObjectWriter * createWinCOFFObjectWriter
> (raw_ostream & OS); }
>
> If you need a function to be visible across files, use a header;
> shortcuts like this make the code more difficult to read.
>
>
On...