From: Manfred Hollstein <manfred@s-direktnet.de>
To: manfred@s-direktnet.de
Cc: law@cygnus.com, Manfred.Hollstein@ks.sel.alcatel.de,
oliva@dcc.unicamp.br, gcc2@cygnus.com, egcs@cygnus.com
Subject: Re: New problems with gcc-2.8.0 based code - NOW FIXED!
Date: Sat, 27 Dec 1997 12:13:00 -0000 [thread overview]
Message-ID: <199712271650.RAA00440@saturn.s-direktnet.de> (raw)
In-Reply-To: <199712261411.PAA00654@saturn.s-direktnet.de>
On Fri, 26 December 1997, 15:11:14, manfred@s-direktnet.de wrote:
> There are other problems since the merge with gcc-2.8.0, though.
>
> Up to egcs-1.0 (incl. egcs-971201) I've been able to built my Linux
> kernel with `-O6 -march=pentium -mcpu=pentium -fomit-frame-pointer
> -malign-loops=0 -malign-jumps=0 -malign-functions=0' _and_
> `-funroll-all-loops'!
>
> Newer snapshots and gcc-2.8.0-971213 don't allow me to do that;
> `-funroll-all-loops' causes `isapnp' and `clock' to fail with
> `segmentation violations'. Omitting `-funroll-all-loops' helps for
> the most current 2.1.7x kernels, but 2.0.33 still fails if compiled by
> gcc-2.8.0 and egcs-971215!
>
> Did anybody else see similar symptoms?
>
> Looks - at least for me - like the loop unrolling stuff (and perhaps
> other as well) hasn't really been improved by the merge with gcc-2.8.0
> :-(
Just compiled my 2.1.76 kernel once again this time using egcs-971225
to see if the `-funroll-all-loops' still persists.
IT'S FIXED!
I writing this e-mail on the freshly compiled kernel and didn't had
any problems so far. I'll only have to reboot later on to sent this
mail out into the world, as ISDN is still broken in the most recent
kernels :-(
Keep up the good work, cheers 1998
Manfred
next prev parent reply other threads:[~1997-12-27 12:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-10 12:02 cannot bootstrap neither gcc-2.8.0-971206 nor egcs-971207 on sparc-sun-sunos4.1.3 Alexandre Oliva
1997-12-10 23:09 ` Manfred.Hollstein
1997-12-11 3:32 ` Paul Eggert
1997-12-11 1:51 ` Manfred.Hollstein
1997-12-22 12:06 ` Jeffrey A Law
1997-12-22 22:04 ` Alexandre Oliva
1997-12-26 8:11 ` New problems with gcc-2.8.0 based code [was: Re: cannot bootstrap neither gcc-2.8.0-971206 nor egcs-971207 on sparc-sun-sunos4.1.3 ] Manfred Hollstein
1997-12-27 12:13 ` Manfred Hollstein [this message]
1997-12-28 23:23 ` New problems with gcc-2.8.0 based code - NOW FIXED! Richard Stallman
1997-12-29 7:48 ` Jeffrey A Law
1997-12-29 11:17 ` Manfred Hollstein
1997-12-29 10:20 ` Jeffrey A Law
1997-12-30 8:57 ` Manfred Hollstein
1997-12-30 9:47 ` Andi Kleen
1998-01-01 10:02 ` Manfred Hollstein
1997-12-30 11:33 ` Philip Blundell
1997-12-30 13:17 ` Paul Koning
1997-12-29 11:08 ` Manfred Hollstein
[not found] <199712302041.MAA25118@atrus.synopsys.com>
1997-12-30 13:45 ` Toon Moene
[not found] <9712301949.AA01218@vlsi1.ultra.nyu.edu>
1997-12-30 13:52 ` Paul Koning
1997-12-30 12:27 ` Linus Torvalds
[not found] <9712302109.AA01369@vlsi1.ultra.nyu.edu>
1997-12-30 14:41 ` Paul Koning
1997-12-30 23:05 ` Richard Stallman
[not found] <9712302324.AA01798@vlsi1.ultra.nyu.edu>
1997-12-30 16:39 ` Paul Koning
[not found] <E0xnN2N-0005UN-00@paddington.london.uk.eu.org>
[not found] ` <199801030231.DAA25241@mail.macqel.be>
1998-01-05 10:13 ` Paul Koning
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=199712271650.RAA00440@saturn.s-direktnet.de \
--to=manfred@s-direktnet.de \
--cc=Manfred.Hollstein@ks.sel.alcatel.de \
--cc=egcs@cygnus.com \
--cc=gcc2@cygnus.com \
--cc=law@cygnus.com \
--cc=oliva@dcc.unicamp.br \
/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).