From: Krister Walfridsson <cato@df.lth.se>
To: Shigeya Suzuki <shigeya@foretune.co.jp>
Cc: egcs@cygnus.com
Subject: Re: recent snapshot fail to compile on BSD/OS
Date: Mon, 13 Apr 1998 09:38:00 -0000 [thread overview]
Message-ID: <Pine.LNX.3.96.980413180435.19758A-100000@bartlet.df.lth.se> (raw)
In-Reply-To: <19980413191851E.shigeya@foretune.co.jp>
On Mon, 13 Apr 1998, Shigeya Suzuki wrote:
> stage1/xgcc -Bstage1/ -DIN_GCC -W -Wall -O2 -g -O2 -DHAVE_CONFIG_H -o gen
> genrtl \
> gengenrtl.o ` case "obstack.o" in ?*) echo obstack.o ;; esac ` ` case "" in ?*)
> echo ;; esac ` ` case "" in ?*) echo ;; esac `
> ./gengenrtl tmp-genrtl.h tmp-genrtl.c
> gmake[2]: *** [s-genrtl] Segmentation fault (core dumped)
> gmake[2]: Leaving directory `/usr/home/shigeya/work/egcs/snap1/gcc'
> gmake[1]: *** [bootstrap] Error 2
> gmake[1]: Leaving directory `/usr/home/shigeya/work/egcs/snap1/gcc'
> gmake: *** [bootstrap] Error 2
This looks like the ASM_OUTPUT_ALIGN problem that {Net,Free,Open}BSD had.
Does this patch (to egcs/gcc/config/i386/bsd386.h) solve your problem?
/Krister
Mon Apr 13 18:07:03 1998 Krister Walfridsson <cato@df.lth.se>
* bsd386.h (ASM_OUTPUT_ALIGN): Redefine.
*** bsd386.h.old Mon Apr 13 17:55:56 1998
--- bsd386.h Mon Apr 13 17:58:05 1998
***************
*** 24,26 ****
--- 24,33 ----
/* Until they use ELF or something that handles dwarf2 unwinds
and initialization stuff better. */
#define DWARF2_UNWIND_INFO 0
+
+ /* BSD/OS still uses old binutils that don't insert nops by default
+ when the .align directive demands to insert extra space in the text
+ segment. */
+ #undef ASM_OUTPUT_ALIGN
+ #define ASM_OUTPUT_ALIGN(FILE,LOG) \
+ if ((LOG)!=0) fprintf ((FILE), "\t.align %d,0x90\n", (LOG))
next prev parent reply other threads:[~1998-04-13 9:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-13 3:22 Shigeya Suzuki
1998-04-13 3:22 ` Shigeya Suzuki
1998-04-13 9:38 ` Krister Walfridsson [this message]
1998-04-14 3:48 ` Shigeya Suzuki
1998-04-14 13:21 ` Jeffrey A Law
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.3.96.980413180435.19758A-100000@bartlet.df.lth.se \
--to=cato@df.lth.se \
--cc=egcs@cygnus.com \
--cc=shigeya@foretune.co.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).