Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: cagney@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit] note non-building architectures
Date: Sun, 01 May 2005 23:32:00 -0000	[thread overview]
Message-ID: <200505012332.j41NWMH0026515@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <42756233.5080809@gnu.org> (message from Andrew Cagney on Sun, 01 May 2005 19:11:47 -0400)

   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.

   -	m68k		--target=m68k-elf ,-Werror
   +	m68k		--target=m68k-elf broken
   +			(opcodes/m68k-dis.c:338 longjmp clober)

   -	vax		--target=vax-netbsd ,-Werror
   +	vax		--target=vax-netbsd broken
   +			(opcodes/vax-dis.c:224 longjmp clober)

Mark


  reply	other threads:[~2005-05-01 23:32 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 [this message]
2005-05-01 23:54   ` Andreas Schwab
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=200505012332.j41NWMH0026515@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.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