From: Andreas Schwab <schwab@suse.de>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: cagney@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [commit] note non-building architectures
Date: Sun, 01 May 2005 23:54:00 -0000 [thread overview]
Message-ID: <jevf62qz88.fsf@sykes.suse.de> (raw)
In-Reply-To: <200505012332.j41NWMH0026515@elgar.sibelius.xs4all.nl> (Mark Kettenis's message of "Mon, 2 May 2005 01:32:22 +0200 (CEST)")
Mark Kettenis <mark.kettenis@xs4all.nl> writes:
> Date: Sun, 01 May 2005 19:11:47 -0400
> From: Andrew Cagney <cagney@gnu.org>
>
> As part of getting ready for GCC 4, I've found that a number of arches
> don't build with gcc-3.4 when using gdb_mbuild.sh. As an aid, and to
> stop me and presumably others from going round in circles, I've updated
> the MAINTAINERS file to both reflect current reality note the problem.
>
> I think your GCC 3.4 is busted. I must admit that I don't really
> understand that longjmp clobber warning message is warning about
> exactly, but returning -1 immediately after a setjmp() call when that
> has been jumped to, seems entirely safe to me.
This is GCC PR21059.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2005-05-01 23:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-01 23:14 Andrew Cagney
2005-05-01 23:32 ` Mark Kettenis
2005-05-01 23:54 ` Andreas Schwab [this message]
2005-05-02 15:58 ` Andrew Cagney
2005-05-02 16:35 ` Mark Kettenis
2005-05-02 16:50 ` Stan Shebs
2005-05-10 3:47 ` Hans-Peter Nilsson
2005-05-19 16:53 ` Andrew Cagney
2005-05-19 19:31 ` Hans-Peter Nilsson
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=jevf62qz88.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
/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