This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/11318] [3.4 regresssion] Spurious bootstrap comparison failures on sparc-sun-solaris
- From: "ehrhardt at mathematik dot uni-ulm dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 26 Jun 2003 09:07:38 -0000
- Subject: [Bug bootstrap/11318] [3.4 regresssion] Spurious bootstrap comparison failures on sparc-sun-solaris
- References: <20030625112358.11318.ehrhardt@mathematik.uni-ulm.de>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11318
------- Additional Comments From ehrhardt at mathematik dot uni-ulm dot de 2003-06-26 09:07 -------
Subject: Re: [3.4 regresssion] Spurious bootstrap comparison failures on sparc-sun-solaris
On Wed, Jun 25, 2003 at 07:17:31PM -0000, zack at gcc dot gnu dot org wrote:
> That should be unnecessary; sparc-sun-solaris should pick up the elfos.h
> TARGET_ASM_FILE_START_FILE_DIRECTIVE setting. Setting it unconditionally
> in sparc/sparc.c will break older (a.out) targets that don't want a .file
> directive.
Unless I'm missing something gcc/config/elfos.h doesn't have a definition
for the TARGET_ASM_FILE_START_FILE_DIRECTIVE macro. The macro is then defined
to 0 in target-def.h. Does this patch look better?
Index: elfos.h
===================================================================
RCS file: /cvsroot/gcc/gcc/gcc/config/elfos.h,v
retrieving revision 1.61
diff -c -r1.61 elfos.h
*** elfos.h 19 Jun 2003 21:47:02 -0000 1.61
--- elfos.h 26 Jun 2003 09:04:08 -0000
***************
*** 230,235 ****
--- 230,239 ----
#undef TARGET_ASM_SELECT_SECTION
#define TARGET_ASM_SELECT_SECTION default_elf_select_section
+ /* Start each asm-file with a .file directive. */
+ #undef TARGET_ASM_FILE_START_FILE_DIRECTIVE
+ #define TARGET_ASM_FILE_START_FILE_DIRECTIVE true
+
/* Define the strings used for the special svr4 .type and .size directives.
These strings generally do not vary from one system running svr4 to
another, but if a given system (e.g. m88k running svr) needs to use
regards Christian