From: Ian Lance Taylor <iant@google.com>
To: "Deepti Sharma" <deepti.gccretarget@gmail.com>
Cc: <gcc-help@gcc.gnu.org>, "'damodar.sonone'" <dsonone@gmail.com>
Subject: Re: upgrading gcc-4.4.0 to gcc-4.7.0:configure: error: cannot compute suffix of object files: cannot compile
Date: Wed, 20 Jun 2012 05:44:00 -0000 [thread overview]
Message-ID: <mcroboezgfd.fsf@dhcp-172-18-216-180.mtv.corp.google.com> (raw)
In-Reply-To: <4fe160f0.e5c4440a.5b5d.75c1@mx.google.com> (Deepti Sharma's message of "Wed, 20 Jun 2012 11:04:19 +0530")
"Deepti Sharma" <deepti.gccretarget@gmail.com> writes:
> After battling with this error for several hours, I was able to resolve this
> error simply by putting my nop instruction pattern as the first pattern.
> Initially, I had movqi as my first instruction pattern. Is this some
> restriction or a bug in gcc?
> ...
> Could you please elaborate on this behaviour? I could not find any such
> restriction in the gcc documentation.
I don't know what the problem is because I don't have any detailed
information about the change you made to GCC.
There is nothing special about the first insn in the MD file. The only
way in which ordering is important is that RTL patterns are matched
against insns in order. It's normally a bug if two insns match an RTL
pattern, but there are unusual cases where that is desirable, and then
order matters.
Ian
next prev parent reply other threads:[~2012-06-20 5:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 4:51 damodar.sonone
2012-06-13 5:09 ` Ian Lance Taylor
2012-06-13 6:04 ` damodar.sonone
2012-06-13 6:18 ` damodar.sonone
2012-06-13 17:31 ` Ian Lance Taylor
2012-06-20 5:34 ` Deepti Sharma
2012-06-20 5:44 ` Ian Lance Taylor [this message]
2012-06-13 11:45 ` Kai Ruottu
2012-06-13 12:50 ` damodar.sonone
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=mcroboezgfd.fsf@dhcp-172-18-216-180.mtv.corp.google.com \
--to=iant@google.com \
--cc=deepti.gccretarget@gmail.com \
--cc=dsonone@gmail.com \
--cc=gcc-help@gcc.gnu.org \
/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).