From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: jan.kratochvil@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: [testsuite commit] Fix -m32 results [Re: [PATCH] Remove some KPASSes in gdb.base/callfuncs.exp]
Date: Wed, 24 Oct 2012 15:05:00 -0000 [thread overview]
Message-ID: <201210241505.q9OF5fOg003231@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <20121024145006.GA29345@host2.jankratochvil.net> (message from Jan Kratochvil on Wed, 24 Oct 2012 16:50:06 +0200)
> Date: Wed, 24 Oct 2012 16:50:06 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
>
> On Wed, 24 Oct 2012 16:35:43 +0200, Mark Kettenis wrote:
> > Your "fix" has an annoying side-effect. Took me a while to figure out
> > where the:
> >
> > Executing on host: gcc -c -o ilp3216410.o ilp3216410.c (timeout = 300)
> > spawn gcc -c -o ilp3216410.o ilp3216410.c
> > Executing on host: gcc -c -o reg6416410.o reg6416410.s (timeout = 300)
> > spawn gcc -c -o reg6416410.o reg6416410.s
> > reg6416410.s: Assembler messages:
> > reg6416410.s:9: Error: bad register name `%r8'
> > reg6416410.s:10: Error: bad register name `%r9'
> > reg6416410.s:11: Error: bad register name `%r10'
> > reg6416410.s:12: Error: bad register name `%r11'
> > reg6416410.s:13: Error: bad register name `%r12'
> > reg6416410.s:14: Error: bad register name `%r13'
> > reg6416410.s:15: Error: bad register name `%r14'
> > reg6416410.s:16: Error: bad register name `%r15'
> > compiler exited with status 1
> > output is:
> > reg6416410.s: Assembler messages:
> > reg6416410.s:9: Error: bad register name `%r8'
> > reg6416410.s:10: Error: bad register name `%r9'
> > reg6416410.s:11: Error: bad register name `%r10'
> > reg6416410.s:12: Error: bad register name `%r11'
> > reg6416410.s:15: Error: bad register name `%r14'
> > reg6416410.s:16: Error: bad register name `%r15'
> >
> > in the middle of my test output came from.
>
> It always happens for those is_ilp32_target & co. functions. But it is only
> in gdb.log, not in gdb.sum.
Well gdb.log is what I actually look at when I'm trying to fix a bug.
Which I did, so the issue is gone from callfuncs.exp. Easier than
arguing about it.
Cheers,
Mark
next prev parent reply other threads:[~2012-10-24 15:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 18:27 [PATCH] Remove some KPASSes in gdb.base/callfuncs.exp Mark Kettenis
2012-10-24 13:48 ` [testsuite commit] Fix -m32 results [Re: [PATCH] Remove some KPASSes in gdb.base/callfuncs.exp] Jan Kratochvil
2012-10-24 14:35 ` Mark Kettenis
2012-10-24 14:50 ` Jan Kratochvil
2012-10-24 15:05 ` Mark Kettenis [this message]
2012-10-24 16:19 ` 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=201210241505.q9OF5fOg003231@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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