From: Phil Muldoon <pmuldoon@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [obv] spu-tdep.c: Compilation error regression
Date: Fri, 12 Nov 2010 13:28:00 -0000 [thread overview]
Message-ID: <m3aalesmdf.fsf@redhat.com> (raw)
In-Reply-To: <20101112124225.GA23529@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Fri, 12 Nov 2010 13:42:25 +0100")
Jan Kratochvil <jan.kratochvil@redhat.com> writes:
> Hi,
>
> recent check-in
> http://sourceware.org/ml/gdb-cvs/2010-11/msg00051.html
> 7d5a91474a0cdb796031ddc25aa0d107be6eb39d
> 2010-11-11 Phil Muldoon <pmuldoon@redhat.com>
> [...]
> * breakpoint.c
> (create_breakpoint_sal): Take a new parameter called internal.
> Call set_breakpoint_number with internal parameter. Do not
> mention internal breakpoints. All callers updated.
> (create_breakpoint): Ditto.
> [...]
>
> broke --enable-targets=all compilation incl. regression testing:
>
> spu-tdep.c: In function ‘spu_catch_start’:
> spu-tdep.c:1899:27: error: expected statement before ‘)’ token
>
> Checked in as obvious.
Ugh, sorry for not catching that.
Thanks
Phil
prev parent reply other threads:[~2010-11-12 13:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 12:43 Jan Kratochvil
2010-11-12 13:28 ` Phil Muldoon [this message]
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=m3aalesmdf.fsf@redhat.com \
--to=pmuldoon@redhat.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).