From: Joe Buck <jbuck@synopsys.COM>
To: pbarada@mail.wm.sps.mot.com (Peter Barada)
Cc: jbuck@synopsys.COM, gcc@gcc.gnu.org
Subject: Re: GCC 3.0.3 Prelease problem on --target=m68k-elf
Date: Fri, 14 Dec 2001 09:05:00 -0000 [thread overview]
Message-ID: <200112141659.IAA22243@atrus.synopsys.com> (raw)
In-Reply-To: <200112141527.fBEFRmd21307@hyper.wm.sps.mot.com> from "Peter Barada" at Dec 14, 2001 10:27:48 AM
Peter Barada:
> >> Unfortunately it doesn't produce correct code for -m5200 due to the
> >> "r" constraint in the following pattern in gcc/config/m68k/m68k.md:
> >>
> >> ;; Jump to variable address from dispatch table of relative addresses.
> >> (define_insn ""
> >> [(set (pc)
> >> (plus:SI (pc)
> >> (sign_extend:SI (match_operand:HI 0 "register_operand" "r"))))
> >> (use (label_ref (match_operand 1 "" "")))]
> >> ""
me:
> >Is this a regression with respect to 3.0.2, or 2.95.3?
Peter:
> Its a regression from 2.95.3, the same problem is in 3.0.2.
Then I don't think it should hold up the 3.0.3 release, since 3.0.3
is an improvement over 3.0.2. But we do want to get it fixed.
> >Either way, it seems the thing to do is to file a bug report with GNATS
> >including a test case for which bad code generation occurs.
>
> Ok, how do I file a bug report with GNATS? I'll have to cobble
> together a test case, but from inspection its obvious that the
> constraint is wrong.
Right, but a test case will be needed for the regression test that whoever
fixes the bug will have to create.
The simplest way is to fire up the "gccbug" program, it will walk you
through the process. (The program is included in the distribution and is
installed when you do a make install).
There's also a web interface: click the GNATS link on http://gcc.gnu.org,
Then click the button for "Create Problem Report".
next prev parent reply other threads:[~2001-12-14 17:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-13 17:12 Peter Barada
2001-12-13 17:39 ` Joe Buck
2001-12-14 7:51 ` Peter Barada
2001-12-14 7:54 ` Craig Rodrigues
2001-12-14 10:18 ` Peter Barada
2001-12-14 9:05 ` Joe Buck [this message]
2001-12-14 16:54 ` Mark Mitchell
2001-12-14 9:00 Bernard Dautrevaux
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=200112141659.IAA22243@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=gcc@gcc.gnu.org \
--cc=pbarada@mail.wm.sps.mot.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).