From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Cc: Pedro Alves <palves@redhat.com>,
Joel Brobecker <brobecker@adacore.com>,
"Hans-Peter Nilsson" <hans-peter.nilsson@axis.com>
Subject: Re: build error for mn10300-elf sim with your recent commit
Date: Sat, 16 Jun 2012 04:56:00 -0000 [thread overview]
Message-ID: <201206160055.51737.vapier@gentoo.org> (raw)
In-Reply-To: <4FDBA5BC.8030300@redhat.com>
[-- Attachment #1: Type: Text/Plain, Size: 1730 bytes --]
On Friday 15 June 2012 17:14:36 Pedro Alves wrote:
> $ cd sim
> $ find . -name "*.[hc]" | xargs grep sysdep.h
> ./d10v/interp.c:#include "sysdep.h"
> ./cr16/interp.c:#include "sysdep.h"
> ./moxie/interp.c:#include "sysdep.h"
> ./mcore/interp.c:#include "sysdep.h"
> ./sh64/sh-desc.c:#include "sysdep.h"
> ./mn10300/interp.c:#include "sysdep.h"
> ./microblaze/interp.c:#include "sysdep.h"
> ./cris/traps.c:/* From ld/sysdep.h. */
> ./cris/cris-desc.c:#include "sysdep.h"
>
> One's a comment. And,
>
> $ find . -name sysdep.h
> ./moxie/sysdep.h
> ./mcore/sysdep.h
> ./microblaze/sysdep.h
>
> So that leaves:
>
> ./d10v/interp.c:#include "sysdep.h"
> ./cr16/interp.c:#include "sysdep.h"
> ./sh64/sh-desc.c:#include "sysdep.h"
> ./mn10300/interp.c:#include "sysdep.h"
> ./cris/cris-desc.c:#include "sysdep.h"
>
> I don't see these ports really caring for hosts other than
> GNU/Linux and Windows.
>
> It is wrong to include bfd/sysdeps.h, practically as much as it
> is wrong to include bfd/config.h. bfd/sysdeps.h HAVE_FOOs depend on
> bfd's own autoconfigury, not the sim's.
>
> Consolidating all the commonality between all these sysdep.h files
> sound nice, though I'm not sure how much work that is.
i'd wager that it's more of a copy & paste error between seems. one of the
really old ones had an interp.c that included sysdep.h, and when someone
started a new port, they copied an existing one. the local sysdep.h wasn't
needed, but the build still worked, so no one looked further. the sim code
base isn't exactly a shining glory of how things should be done :).
i vote for deleting all sysdep.h inclusions where the port doesn't have a
local sysdep.h.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-16 4:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 18:46 Hans-Peter Nilsson
2012-06-15 18:56 ` Joel Brobecker
2012-06-15 19:15 ` Joel Brobecker
2012-06-15 19:39 ` Pedro Alves
2012-06-15 19:52 ` Joel Brobecker
2012-06-15 21:15 ` Pedro Alves
2012-06-16 4:56 ` Mike Frysinger [this message]
2012-06-16 5:09 ` Hans-Peter Nilsson
2012-06-17 18:57 ` Hans-Peter Nilsson
2012-06-17 23:34 ` Mike Frysinger
2012-06-18 18:39 ` Joel Brobecker
2012-06-15 20:37 ` 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=201206160055.51737.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=hans-peter.nilsson@axis.com \
--cc=palves@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