Re: [Bug gas/2971] Slash-star comments don't work for some x86 targets
Hi Neil, If the following condition is met, line_comment_chars consists of just #: #if (defined (TE_I386AIX) \ || ((defined (OBJ_ELF) || defined (OBJ_MAYBE_ELF)) \ !defined (TE_LINUX) \ !defined (TE_NETWARE) \ !defined (TE_FreeBSD) \ !defined (TE_NetBSD))) The problem can be seen with the i386-elf-as cross assembler from the DarwinPorts i386-elf-binutils package on MacOS X on an Intel Mac (and I presume on a PowerPC Mac too). I can reproduce the problem with a file called test.S consisting of just these two lines: Hmm - I think that those sources must be different from the official binutils sources. In our sources the above piece of code looks like this: #if (defined (TE_I386AIX) \ || ((defined (OBJ_ELF) || defined (OBJ_MAYBE_ELF)) \ !defined (TE_GNU) \ !defined (TE_LINUX) \ !defined (TE_NETWARE) \ !defined (TE_FreeBSD) \ !defined (TE_NetBSD))) /* This array holds the chars that always start a comment. If the pre-processor is disabled, these aren't very useful. The option --divide will remove '/' from this list. */ const char *i386_comment_chars = #/; #define SVR4_COMMENT_CHARS 1 #define PREFIX_SEPARATOR '\\' #else const char *i386_comment_chars = #; #define PREFIX_SEPARATOR '/' #endif /* This array holds the chars that only start a comment at the beginning of a line. If the line seems to have the form '# 123 filename' .line and .file directives will appear in the pre-processed output. Note that input_file.c hand checks for '#' at the beginning of the first line of the input file. This is because the compiler outputs #NO_APP at the beginning of its output. Also note that comments started like this one will always work if '/' isn't otherwise defined. */ const char line_comment_chars[] = #/; So line_comment_chars always contains a forward slash, regardless of the settings of any defined constants. I think that you may need to report this problem to the Darwin developers. Cheers Nick ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug gas/2971] Slash-star comments don't work for some x86 targets
--- Additional Comments From nickc at redhat dot com 2006-08-09 08:29 --- Subject: Re: Slash-star comments don't work for some x86 targets Hi Neil, If the following condition is met, line_comment_chars consists of just #: #if (defined (TE_I386AIX) \ || ((defined (OBJ_ELF) || defined (OBJ_MAYBE_ELF)) \ !defined (TE_LINUX) \ !defined (TE_NETWARE) \ !defined (TE_FreeBSD) \ !defined (TE_NetBSD))) The problem can be seen with the i386-elf-as cross assembler from the DarwinPorts i386-elf-binutils package on MacOS X on an Intel Mac (and I presume on a PowerPC Mac too). I can reproduce the problem with a file called test.S consisting of just these two lines: Hmm - I think that those sources must be different from the official binutils sources. In our sources the above piece of code looks like this: #if (defined (TE_I386AIX) \ || ((defined (OBJ_ELF) || defined (OBJ_MAYBE_ELF))\ !defined (TE_GNU) \ !defined (TE_LINUX) \ !defined (TE_NETWARE) \ !defined (TE_FreeBSD) \ !defined (TE_NetBSD))) /* This array holds the chars that always start a comment. If the pre-processor is disabled, these aren't very useful. The option --divide will remove '/' from this list. */ const char *i386_comment_chars = #/; #define SVR4_COMMENT_CHARS 1 #define PREFIX_SEPARATOR '\\' #else const char *i386_comment_chars = #; #define PREFIX_SEPARATOR '/' #endif /* This array holds the chars that only start a comment at the beginning of a line. If the line seems to have the form '# 123 filename' .line and .file directives will appear in the pre-processed output. Note that input_file.c hand checks for '#' at the beginning of the first line of the input file. This is because the compiler outputs #NO_APP at the beginning of its output. Also note that comments started like this one will always work if '/' isn't otherwise defined. */ const char line_comment_chars[] = #/; So line_comment_chars always contains a forward slash, regardless of the settings of any defined constants. I think that you may need to report this problem to the Darwin developers. Cheers Nick -- http://sourceware.org/bugzilla/show_bug.cgi?id=2971 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug gas/2971] Slash-star comments don't work for some x86 targets
--- Additional Comments From caffer at cs dot ucc dot ie 2006-08-09 16:09 --- This bug report is against version 2.16.1. The bug does indeed seem to be fixed in 2.17. I had looked at the overall project changelog for 2.17 but didn't see anything I thought was relevant. Sorry for the confusion. Regards, Neil -- http://sourceware.org/bugzilla/show_bug.cgi?id=2971 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug binutils/2993] compile error bfd.c: noreturn function does return
--- Additional Comments From amylaar at gcc dot gnu dot org 2006-08-09 19:11 --- (In reply to comment #0) I am seeing the same problem for sparc-sun-solaris2.8 X sh-elf, using gcc 2.95.2, when trying to build binutils checked out from the CVS repository today. The bfd.c.patch allows the build to continue past the bfd.c compilation. -- http://sourceware.org/bugzilla/show_bug.cgi?id=2993 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug binutils/3017] New: binutils/doc/Makefile.in uses syntax not accepted by solaris /bin/sh
After applying the patch for PR 2993, the build fails a bit later: Making info in doc rm -f config.texi eval `grep '^ *VERSION=' ../../../src-20060809/binutils/doc/../../bfd/configure`; \ echo @set VERSION $VERSION config.texi echo @set UPDATED `date +%B %Y` config.texi sh: : cannot execute *** Error code 1 make: Fatal error: Command failed for target `config.texi' AFAICT the solaris /bin/sh doesn't consider s as properly nested inside `s. $ echo @set UPDATED `date +%B %Y` : cannot execute @set UPDATED August %Y $ echo @set UPDATED `date '+%B %Y'` @set UPDATED August 2006 -- Summary: binutils/doc/Makefile.in uses syntax not accepted by solaris /bin/sh Product: binutils Version: 2.18 (HEAD) Status: NEW Severity: normal Priority: P2 Component: binutils AssignedTo: unassigned at sources dot redhat dot com ReportedBy: amylaar at gcc dot gnu dot org CC: bug-binutils at gnu dot org GCC host triplet: sparc-sun-solaris2.8 GCC target triplet: sh-elf BugsThisDependsOn: 2993 http://sourceware.org/bugzilla/show_bug.cgi?id=3017 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
Multiple setting of a symbol
Hi, I recently upgraded to as(1) version 2.16.91 20060320, as distributed by CodeSourcery for ARM, and notice differences with regards to earlier versions of as(1) (2.16), as built by myself. (This has caused a lot of head scratching for me). I can reproduce this behavior with the native as 2.17.50 20060709, as distributed with Cygwin for x86. Specifically, given the code my_variable: .long X X = 1 X = 2 the new version assembles the value 1 into my_variable, while the old version assembles the value 2. (Naturally, in real code, X is determined by various macros, etc.) I feel that 2 is the correct value for my_variable, since it is the value of the symbol X in the object file's symbol table. I have found the following workaround my_variable: .long X1 X = 1 X = 2 X1 = X The following workaround does not work: .globl X .long X X = 1 X = 2 Interestingly, .globl X1 .long X1 X = 1 X = 2 X1 = X does. I also have seen absolute symbols (which show properly in the listing produced by -as) being suppressed in the symbol table, not showing up in the output of nm, objdump -t or available to gdb. However, I do not have a test case for this. Regards, Konrad Schwarz BEGIN:VCARD VERSION:2.1 N:Schwarz;Konrad FN:Konrad Schwarz ORG:Siemens AG;CT SE 2 TITLE:Principal Engineer TEL;WORK;VOICE:+49 (89) 636-53579 TEL;WORK;FAX:+49 (89) 636-45450 ADR;WORK;ENCODING=QUOTED-PRINTABLE:;53 518;Siemens AG=0D=0ACT SE 2;M=FCnchen;;81730;Germany LABEL;WORK;ENCODING=QUOTED-PRINTABLE:53 518=0D=0ASiemens AG=0D=0ACT SE 2=0D=0AM=FCnchen 81730=0D=0AGermany ADR;POSTAL;ENCODING=QUOTED-PRINTABLE:;;Siemens AG=0D=0ACT SE 2;M=FCnchen;;81730;Germany LABEL;POSTAL;ENCODING=QUOTED-PRINTABLE:Siemens AG=0D=0ACT SE 2=0D=0AM=FCnchen 81730=0D=0AGermany EMAIL;PREF;INTERNET:[EMAIL PROTECTED] REV:20060130T101011Z END:VCARD ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
