From: Ian Lance Taylor <iant@google.com>
To: "Andreas Geißler" <setjem@googlemail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: pr26180.c
Date: Wed, 14 Nov 2012 14:54:00 -0000 [thread overview]
Message-ID: <CAKOQZ8z_pmCLx4YXxuBXsxBUNkeyAEH4zw-aVAR89nn1Bij8Kg@mail.gmail.com> (raw)
In-Reply-To: <CAF-06ZXmZ0uZxrghNRghRxnTAbYQDNirdb1CRqkz9LbERuzixA@mail.gmail.com>
On Wed, Nov 14, 2012 at 5:37 AM, Andreas Geißler <setjem@googlemail.com> wrote:
>
> So i you would like to ask you, which special pattern (machine
> description pattern (*.md))
> is related to "x2 = ((x > 0)? (x): -(x));" or where should i search the problem.
The way to debug this kind of problem is to run GCC with
-fdump-rtl-all. Then read the RTL files back to front until you find
the place where the generated code is erroneous. For a
machine-specific problem like this it will normally happen sometime in
the register allocation pass or later.
Ian
next prev parent reply other threads:[~2012-11-14 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 13:37 pr26180.c Andreas Geißler
2012-11-14 14:54 ` Ian Lance Taylor [this message]
2012-11-14 15:06 ` pr26180.c Andreas Geißler
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=CAKOQZ8z_pmCLx4YXxuBXsxBUNkeyAEH4zw-aVAR89nn1Bij8Kg@mail.gmail.com \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=setjem@googlemail.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).