public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bernd.edlinger at hotmail dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/65067] regression on accessing volatile bit field
Date: Wed, 04 Mar 2015 20:20:00 -0000 [thread overview]
Message-ID: <bug-65067-4-vYJ5Yygr0n@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65067-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65067
--- Comment #8 from Bernd Edlinger <bernd.edlinger at hotmail dot de> ---
Created attachment 34955
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34955&action=edit
Proposed Fix
Well, I noticed that the first version of this patch caused
a small but measurable decrease of code quality on x86_64,
so I moved the patch to the if (strict_volatile_bitfield_p block,
and used some code transformations to simplify the resulting code
a bit.
I will post this new version for review, after a full boot-strap
and successful regression-test on my ARM target.
next prev parent reply other threads:[~2015-03-04 20:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-65067-4@http.gcc.gnu.org/bugzilla/>
2015-02-16 8:58 ` rguenth at gcc dot gnu.org
2015-02-16 9:05 ` terry.guo at arm dot com
2015-02-16 9:13 ` rguenther at suse dot de
2015-02-16 18:28 ` bernd.edlinger at hotmail dot de
2015-02-26 9:39 ` tony.liu at arm dot com
2015-03-01 13:04 ` bernd.edlinger at hotmail dot de
2015-03-04 2:29 ` tony.liu at arm dot com
2015-03-04 20:20 ` bernd.edlinger at hotmail dot de [this message]
2015-03-05 5:44 ` tony.liu at arm dot com
2015-03-05 18:57 ` edlinger at gcc dot gnu.org
2015-04-22 18:58 ` ramana at gcc dot gnu.org
2015-04-22 19:11 ` bernd.edlinger at hotmail dot de
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-65067-4-vYJ5Yygr0n@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).