From: H.J. Lu <hjl@lucon.org>
To: egcs@cygnus.com
Subject: egcs 970828 and X11 on linux/x86
Date: Sun, 31 Aug 1997 02:07:35 -0000 [thread overview]
Message-ID: <m0x54aR-0004ecC@ocean.lucon.org> (raw)
Hi,
On linux/x86, I bootstapped egcs 970828 with -O -g and used that egcs
to compile egcs with -O6 -fomit-frame-pointer. Then I used that
compiler to compile XFree86 3.3.1 with -O6 -fno-exceptions. I didn't
see any problems with the rebuilt XFree86 3.3.1.
BTW, I applied Jim's patch to i386.c:
Wed Aug 27 14:52:54 1997 Jim Wilson
* i386.c (ix86_expand_epilogue): Emit blockage instruction when pic.
Without it, shared libraries may be miscompiled with -O2/-O3 or above.
--
H.J. Lu (hjl@gnu.ai.mit.edu)
WARNING: multiple messages have this Message-ID
From: James Macnicol <J.Macnicol@student.anu.edu.au>
To: egcs@cygnus.com
Subject: Shared C++ libs on i386-pc-solaris2.5.1
Date: Sun, 31 Aug 1997 13:17:41 -0000 [thread overview]
Message-ID: <m0x54aR-0004ecC@ocean.lucon.org> (raw)
Message-ID: <19970831131741.qXeeYibmiMOq0LvIzNVYyelZRDfVs1a2nJv9g1PPZMA@z> (raw)
Hello,
Has anyone managed to build egcs under Solaris x86 2.5.1?
I cannot get any shared C++ libraries to link (including the
libstdc++.so that is built as part of the distribution -- see below),
make[2]: Leaving directory `/export/home/opt/egcs-970828/libio'
/export/home/opt/egcs-970828/gcc/xgcc
-B/export/home/opt/egcs-970828/gcc/ -g -O2 -fno-implicit-templates -h
libstdc++.so.2.8.0 -shared -o libstdc++.so.2.8.0 `cat piclist` -lm
Text relocation remains referenced
against symbol offset in file
__eh_type 0xe3
/export/home/opt/egcs-970828/gcc/libgcc.a(_eh.o)
__eh_type 0x36a
/export/home/opt/egcs-970828/gcc/libgcc.a(exception.o)
[snip]
__eh_cleanup 0x243
/export/home/opt/egcs-970828/gcc/libgcc.a(exception.o)
[snip]
__eh_in_catch 0x448
/export/home/opt/egcs-970828/gcc/libgcc.a(exception.o)
__get_dynamic_handler_chain 0x50a
/export/home/opt/egcs-970828/gcc/libgcc.a(tinfo.o)
[snip]
__terminate 0x325
/export/home/opt/egcs-970828/gcc/libgcc.a(exception.o)
[snip]
__sjthrow 0x24c
/export/home/opt/egcs-970828/gcc/libgcc.a(exception.o)
[snip]
There are a lot more errors than this, including references to stdc
things
malloc, free etc. I just tried did a normal configure with
--enable-shared
and let it run (I built gcc in three stages by hand since make from
the toplevel directory doesn't seem to do that). I am using the
standard
Sun assembler and linker (I realize C++ debugging won't work but I can
live with that for now).
Any ideas?
--
James Macnicol
J.Macnicol@student.anu.edu.au
http://goblet.anu.edu.au/~m9305357/home.html
WARNING: multiple messages have this Message-ID
From: Allen Briggs <briggs@puma.macbsd.com>
To: egcs@cygnus.com
Subject: Small patch for NetBSD
Date: Sun, 31 Aug 1997 16:37:13 -0000 [thread overview]
Message-ID: <m0x54aR-0004ecC@ocean.lucon.org> (raw)
Message-ID: <19970831163713.dT19kAvZFdczoPRntxMD_D26BPpMKH-ksCUFIbfX6bw@z> (raw)
NetBSD declares sys_errlist--this caused the texinfo compile to break
since it also declares sys_errlist (for mystrerror()). I won't bother
sending in a patch for that since I compiled the current texinfo with
no trouble recently. However,
NetBSD has defined sys_siglist since version 1.0. Here is a patch
that allows the 970828 collect2.c to compile when configured for
m68k-unknown-netbsd1.2g:
Sun Aug 31 11:38:55 1997 Allen Briggs (briggs@macbsd.com)
* netbsd.h: Define DONT_DECLARE_SYS_SIGLIST if >= NetBSD 1.0.
::::::::::::::::::::::::::::::::::::::::::::::::::
*** /tmp/netbsd.h Sun Aug 31 11:45:24 1997
--- gcc/config/netbsd.h Sun Aug 31 12:32:20 1997
***************
*** 34,39 ****
--- 34,40 ----
#endif
+ #include
/* Provide a CPP_SPEC appropriate for NetBSD. Current we just deal with
the GCC option `-posix'. */
***************
*** 65,70 ****
--- 66,78 ----
#define SWITCH_TAKES_ARG(CHAR) \
(DEFAULT_SWITCH_TAKES_ARG(CHAR) \
|| (CHAR) == 'R')
+
+ /* NetBSD 1.0 and later have sys_siglist in signal.h, but current
+ numbering drops the last digit (i.e., numbering is now YYYYMM). */
+
+ #if (NetBSD > 1993070 || NetBSD
WARNING: multiple messages have this Message-ID
From: Kamil Iskra <kamil@dwd.interkom.pl>
To: egcs@cygnus.com
Subject: Re: Strange warning (variable might be clobbered by `longjmp' or `vfork')
Date: Sun, 31 Aug 1997 18:57:24 -0000 [thread overview]
Message-ID: <m0x54aR-0004ecC@ocean.lucon.org> (raw)
Message-ID: <19970831185724.Ivz9ipSfc8TkHuU1gyx7o9cp19sAgRdffnBIxuht2AU@z> (raw)
In-Reply-To: 199708310123.SAA21826@cygnus.com
On Sat, 30 Aug 1997, Jim Wilson wrote:
> The following code gives a strange warning.
> ~/Prog> g++ -Wall -O -c egcs-feature2.cc
> egcs-feature2.cc: In function `void f()':
> egcs-feature2.cc:15: warning: variable `int maxrows' might be clobbered by
> `longjmp' or `vfork'
[snip]
> This can probably be fixed by making the sjlj EH support and flow interact
> better.
Actually, is this particular warning a really useful feature, that saves
people from making a bug every other day? I don't think so. To the
contrary, I've seen it several times and every time it was bogus. Perhaps
it would be better to just get rid of this warning?
/ Kamil Iskra - AMIGA 1200, 68030 50MHz, HDD 1.6 GB, 18 MB RAM \
| iskra@student.uci.agh.edu.pl kiskra@ernie.icslab.agh.edu.pl |
| http://student.uci.agh.edu.pl/~iskra |
\ PGP public key available via Finger or WWW /
next reply other threads:[~1997-08-31 2:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-31 2:07 H.J. Lu [this message]
1997-08-31 13:17 ` Shared C++ libs on i386-pc-solaris2.5.1 James Macnicol
1997-08-31 16:37 ` Small patch for NetBSD Allen Briggs
1997-08-31 18:57 ` Strange warning (variable might be clobbered by `longjmp' or `vfork') Kamil Iskra
1997-08-31 18:57 erase operation in STL Weiwen Liu
1997-08-31 21:31 ` egcs 970828 and X11 on linux/x86 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=m0x54aR-0004ecC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=egcs@cygnus.com \
/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).