public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/53272] wrong condition-codes for strict-low-part destination and small-integer source
Date: Tue, 08 May 2012 00:17:00 -0000 [thread overview]
Message-ID: <bug-53272-4-0qA3CUrEIv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53272-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53272
Hans-Peter Nilsson <hp at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2012-05-08
AssignedTo|unassigned at gcc dot |hp at gcc dot gnu.org
|gnu.org |
Ever Confirmed|0 |1
--- Comment #1 from Hans-Peter Nilsson <hp at gcc dot gnu.org> 2012-05-08 00:11:03 UTC ---
Created attachment 27337
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27337
testcase to be compiled with -O2
The effect of the bug is to eliminate the NULL-pointer check for rtc->ops->f
and always call it, which is not a good idea when it is NULL. Test-case
derived from a Linux driver.
Unfortunately, presence of a main function makes the bug hide by slightly
changing the generated code, so I have to put the framework in a separate file
to make a runnable test-case. This is a secondary bug, for which I will clone a
PR from this PR: with the marker-asms and attributes noclone, noinline, there
should be no need for that. It seems static branch predictions change.
next prev parent reply other threads:[~2012-05-08 0:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 0:11 [Bug target/53272] New: " hp at gcc dot gnu.org
2012-05-08 0:17 ` hp at gcc dot gnu.org [this message]
2012-05-08 15:22 ` [Bug target/53272] " hp at gcc dot gnu.org
2012-05-08 15:27 ` hp at gcc dot gnu.org
2012-05-08 15:27 ` hp at gcc dot gnu.org
2012-05-08 15:35 ` hp at gcc dot gnu.org
2012-05-08 15:37 ` hp at gcc dot gnu.org
2012-05-08 15:45 ` hp at gcc dot gnu.org
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=bug-53272-4-0qA3CUrEIv@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).