Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@gnu.org>
To: cagney@gnu.org
Cc: gdb@sources.redhat.com
Subject: Re: [PATCH/RFA] sim autoconf conversion fallout
Date: Tue, 18 Jan 2005 20:35:00 -0000	[thread overview]
Message-ID: <200501182035.j0IKZcrn004218@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <41ED6BFD.6060602@gnu.org> (message from Andrew Cagney on Tue, 18 Jan 2005 15:05:17 -0500)

   Date: Tue, 18 Jan 2005 15:05:17 -0500
   From: Andrew Cagney <cagney@gnu.org>

   Mark Kettenis wrote:
   > There still a lot of breakage in the sim tree:

   Looks under desk, nope, no fire.  I guess MIPS, mn10300, and erc32 
   qualify as "a lot" :-)

I just tried to build a native GDB on mips64-unknown-openbsd3.6 and
sparc64-unknown-freebsd5.3 in a row.  Gave me a slightly biased view
of reality ;-).  It seems though that d10v is also broken.

   > * Several simulators no longer build because the common directory
   >   isn't configured.  AFAICT all similators need that directory, so I
   >   propose the attached patch.

   This problem applied to just two simulators:  MIPS and mn10300.  I've 
   fixed the error and confirmed that the MIPS builds.

Thanks for fixing it.  However, what's against configuring the common
directory unconditionally?  Makes things even simpler ;-).

   > * The --enable-sim option is essentially a no-op now, since all
   >   simulators are built unconditionally if gdb is configured for a
   >   matching target.  Why has the option been retained while all the
   >   logic that used it is gone?  Why was the logic removed in the first
   >   place?

   --enable-sim always was a no-op (unlike --disable-sim).   The only 
   exception was for erc32 and since that doesn't build at all I've now 
   disabled it.

Ah, I overlooked the "if test "${enable_sim}" != no".

   > * In the past several simulators were only built when compiling with
   >   gcc.  That code was ripped out.  Why?

   Why not.

    From '98 (although I suspect '96):
      # The PowerPC simulator uses the GCC extension long long as well as
      # ANSI prototypes, so don't enable it for random host compilers
      # unless asked to.
   hence the test.

   Fast forward 7 years - even GCC now assums ISO-C and long-long is a 
   defacto "standard".

With erc32 gone this seems not unreasonable.  If "long long" poses a
problem we can always bring over some of the logic from bfd.

Mark


  reply	other threads:[~2005-01-18 20:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-16 19:26 Mark Kettenis
2005-01-18 20:07 ` Andrew Cagney
2005-01-18 20:35   ` Mark Kettenis [this message]
2005-01-18 21:05     ` Andrew Cagney
2005-01-19 10:05       ` Richard Earnshaw
2005-01-17  2:28 Paul Schlie

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=200501182035.j0IKZcrn004218@elgar.sibelius.xs4all.nl \
    --to=kettenis@gnu.org \
    --cc=cagney@gnu.org \
    --cc=gdb@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