public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frédéric L . W . Meunier  <0@pervalidus.net>
To: linux-kernel@vger.kernel.org
Subject: Re: gcc-2.95.2-51 is buggy
Date: Fri, 24 Nov 2000 06:09:42 -0200	[thread overview]
Message-ID: <20001124060942.B26543@pervalidus.dyndns.org> (raw)

Andries.Brouwer@cwi.nl wrote:

<skip>
> % /usr/gcc/aeb/bin/gcc -v
> Reading specs from
> /usr/gcc/aeb/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/specs
> gcc version 2.95.2 19991024 (release)gcc version 2.95.2 19991024 (release)
> % /usr/gcc/aeb/bin/gcc -Wall -O2 -o nobug bug.c; ./nobug
> 0x0

Interesting. On a Slackware 7.1 recently upgraded to glibc 2.2
(and where gcc 2.95.2 from ftp.gnu.org was built because 2.2
requires this version) I get:

% gcc -Wall -O2 -o bug bug.c
% ./bug
0x84800000

% egcs-2.91.66 -Wall -O2 -o bug bug.c
% ./bug
0x0

% gcc -Wall -O -o bug bug.c
% ./bug
0x0

% gcc -v
Reading specs from
/usr/lib/gcc-lib/i386-slackware-linux/2.95.2/specs
gcc version 2.95.2 19991024 (release)

% egcs-2.91.66 -v
Reading specs from
/usr/lib/gcc-lib/i386-slackware-linux/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)

Slackware's -current tree was upgraded to glibc 2.2 and gcc
2.95.2, but I built them myself.

-- 
0@pervalidus.{net, com, dyndns.org}
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2000-11-24  8:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-24  8:09 Frédéric L . W . Meunier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-11-27 14:28 gcc-2.95.2-51 is buggy Pavel Pisa;research student
2000-11-24 13:04 Mikael Pettersson
2000-11-24 12:48 Andries.Brouwer
2000-11-24 16:46 ` Matthew Vanecek
2000-11-24  5:20 Andries.Brouwer
2000-11-24  5:44 ` Neil Brown
2000-11-24  6:47   ` Alexander Viro
2000-11-25 17:26   ` Rik van Riel
2000-11-25 19:16     ` Jeff V. Merkey
2000-11-25 20:01     ` Andries Brouwer
2000-11-25 20:06       ` Rik van Riel
2000-11-26 15:33         ` Olaf Dietsche
2000-11-26 16:58           ` Rik van Riel
2000-11-26 19:36           ` Mike Castle
2000-11-26 19:41             ` Russell King
2000-11-26 19:55           ` J . A . Magallon
2000-11-24  9:37 ` Ion Badulescu
2000-11-24 10:18   ` Linux Kernel Developer
2000-11-24  9:57 ` Jakub Jelinek

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=20001124060942.B26543@pervalidus.dyndns.org \
    --to=0@pervalidus.net \
    --cc=linux-kernel@vger.kernel.org \
    /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