From: cgd@broadcom.com
To: "Andrew Cagney" <ac131313@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: problem w/ igen, multiple -M models, and -G gen-multi-sim.
Date: Thu, 14 Mar 2002 21:20:00 -0000 [thread overview]
Message-ID: <yov5sn72tnix.fsf@broadcom.com> (raw)
In-Reply-To: "Andrew Cagney"'s message of "Thu, 14 Mar 2002 21:46:08 -0500"
At Thu, 14 Mar 2002 21:46:08 -0500, Andrew Cagney wrote:
> Turns out that such instructions need to be given unique field-names as
> they would otherwise generate functions with the same name.
Right. In the example, yes, they had unique field names, but until
your patch that had no effect.
(still don't need/want to use the feature, but better to have it
fixed than not. 8-)
> See attached. It works for your example.
Are you planning to check it in after a delay or some futher testing
on your end? or you want me/others to throw it into our source trees
and it a spin to mmake sure it doesn't break anything?
thanks,
chris
next prev parent reply other threads:[~2002-03-15 5:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-12 12:47 cgd
2002-03-14 18:46 ` Andrew Cagney
2002-03-14 21:20 ` cgd [this message]
2002-03-14 22:21 ` Andrew Cagney
2002-03-23 16:46 ` Andrew Cagney
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=yov5sn72tnix.fsf@broadcom.com \
--to=cgd@broadcom.com \
--cc=ac131313@cygnus.com \
--cc=gdb@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