public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org, aburgess@redhat.com
Subject: Re: sim regen preparation
Date: Wed, 16 Aug 2023 12:37:56 +0930	[thread overview]
Message-ID: <ZNw9jG/7XJN1JoL4@squeak.grove.modra.org> (raw)
In-Reply-To: <87a5utzj2z.fsf@tromey.com>

On Mon, Aug 14, 2023 at 10:26:12AM -0600, Tom Tromey wrote:
> >>>>> "Alan" == Alan Modra via Gdb-patches <gdb-patches@sourceware.org> writes:
> 
> Alan> Regerating sim loses commit 1be79b1ebfad from sim/lm32/cpu.h, a
> Alan> generated file, so this patch move those declarations to
> Alan> sim/lm32/sim-main.h.
> 
> In other spots in gdb we stick a read-only header on generated files to
> avoid this sort of error, like:
> 
> /* THIS FILE IS GENERATED -*- buffer-read-only: t -*- */
> /* vi:set ro: */
> 
> Pity cgen doesn't do this.

Yes, that would be nice.  Along with a whole lot of other things.  :)

> Alan> OK to apply?
> 
> I don't mind the patch at all but I wonder why cgen generates calls to
> these functions but not declarations for them; whereas for other
> functions (e.g., "lm32bf_h_pc_get") it does generate the declarations.

I'm not curious enough to dive down that rabbit hole, sorry.  The sim
patches I posted were enough for me to regen and run the testsuite, so
that eg. cpu/ patches can be regression tested on sim targets.  I also
looked at regenerated files in enough detail to convince myself that
the changes, in particular to iq2000, were reasonable.  

Note that people might have thought they were testing sim, but "make
check" in sim doesn't do much unless you set up site-sim-config.exp,
or have a lot of AS_FOR_TARGET_$arch, LD_FOR_TARGET_$arch and
CC_FOR_TARGET_$arch in your environment.  Also, linker warnings render
many of the tests "UNTESTED".  Only the latter is fixed, and of course
only for current warnings.

-- 
Alan Modra
Australia Development Lab, IBM

  reply	other threads:[~2023-08-16  3:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-14 11:58 Alan Modra
2023-08-14 16:26 ` Tom Tromey
2023-08-16  3:07   ` Alan Modra [this message]
2023-08-16  3:51     ` Sam James
2023-08-16 13:20       ` Alan Modra
2023-08-16 17:47     ` Tom Tromey

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=ZNw9jG/7XJN1JoL4@squeak.grove.modra.org \
    --to=amodra@gmail.com \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).