From: Orjan Friberg <orjan.friberg@axis.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/CRIS] Prologue scan bug fixes, return_value implementation
Date: Thu, 04 Mar 2004 09:23:00 -0000 [thread overview]
Message-ID: <4046F56F.3010402@axis.com> (raw)
In-Reply-To: <40462836.1080706@gnu.org>
Andrew Cagney wrote:
>
> Yes. Since the absolute worst possible outcome for such a commit is you
> breaking the CRIS architecture, it is entirely up to you to decide if
> its worth the risk :-)
78 new PASS in gdb.base makes it worth the risk ;-). (Committed to trunk and
branch.)
--
Orjan Friberg
Axis Communications
WARNING: multiple messages have this Message-ID
From: Orjan Friberg <orjan.friberg@axis.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/CRIS] Prologue scan bug fixes, return_value implementation
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <4046F56F.3010402@axis.com> (raw)
Message-ID: <20040319000900.gv5nj8x_x84KSS-3GuxnV0LT_ehh9Cn3EdBkJvfw30s@z> (raw)
In-Reply-To: <40462836.1080706@gnu.org>
Andrew Cagney wrote:
>
> Yes. Since the absolute worst possible outcome for such a commit is you
> breaking the CRIS architecture, it is entirely up to you to decide if
> its worth the risk :-)
78 new PASS in gdb.base makes it worth the risk ;-). (Committed to trunk and
branch.)
--
Orjan Friberg
Axis Communications
next prev parent reply other threads:[~2004-03-04 9:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 0:09 Orjan Friberg
2004-03-03 16:40 ` Orjan Friberg
2004-03-03 16:44 ` Daniel Jacobowitz
2004-03-19 0:09 ` Orjan Friberg
2004-03-03 16:59 ` Orjan Friberg
2004-03-19 0:09 ` Andrew Cagney
2004-03-03 18:47 ` Andrew Cagney
2004-03-04 9:23 ` Orjan Friberg [this message]
2004-03-19 0:09 ` Orjan Friberg
2004-03-19 0:09 ` Daniel Jacobowitz
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=4046F56F.3010402@axis.com \
--to=orjan.friberg@axis.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@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