public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug middle-end/45274] __restrict__ type qualifier does not work on pointers to bitfields
[not found] <bug-45274-4@http.gcc.gnu.org/bugzilla/>
@ 2010-10-28 20:05 ` pinskia at gcc dot gnu.org
2011-04-11 20:13 ` pinskia at gcc dot gnu.org
2021-12-22 9:53 ` [Bug tree-optimization/45274] " pinskia at gcc dot gnu.org
2 siblings, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2010-10-28 20:05 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45274
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|powerpc64-unknown-linux-gnu |powerpc64-unknown-linux-gnu
| |, mips64-elf
Status|UNCONFIRMED |NEW
Last reconfirmed| |2010.10.28 20:05:42
Ever Confirmed|0 |1
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> 2010-10-28 20:05:42 UTC ---
Expand has the issue:
(insn 7 6 8 t2.c:7 (set (reg:SI 197)
(mem/s:SI (reg/v/f:DI 193 [ src ]) [0 S4 A32])) -1 (nil))
Notice the aliasing set of 0.
Confirmed.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug middle-end/45274] __restrict__ type qualifier does not work on pointers to bitfields
[not found] <bug-45274-4@http.gcc.gnu.org/bugzilla/>
2010-10-28 20:05 ` [Bug middle-end/45274] __restrict__ type qualifier does not work on pointers to bitfields pinskia at gcc dot gnu.org
@ 2011-04-11 20:13 ` pinskia at gcc dot gnu.org
2021-12-22 9:53 ` [Bug tree-optimization/45274] " pinskia at gcc dot gnu.org
2 siblings, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2011-04-11 20:13 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45274
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Target|powerpc64-unknown-linux-gnu |
|, mips64-elf |
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> 2011-04-11 20:13:25 UTC ---
(In reply to comment #1)
> I don't think this has anything to do with restrict and all with lowering
> bitfield accesses only during expansion, and at RTL level the bitfield
> operations being too big for combiner to optimize them.
No this is unrelated to the combiner not be able to optimize the bitfield
accesses. Rather it is related to how store and loads happen on bitfields. We
don't try to keep track of individual bits for a change in the store.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug tree-optimization/45274] __restrict__ type qualifier does not work on pointers to bitfields
[not found] <bug-45274-4@http.gcc.gnu.org/bugzilla/>
2010-10-28 20:05 ` [Bug middle-end/45274] __restrict__ type qualifier does not work on pointers to bitfields pinskia at gcc dot gnu.org
2011-04-11 20:13 ` pinskia at gcc dot gnu.org
@ 2021-12-22 9:53 ` pinskia at gcc dot gnu.org
2 siblings, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2021-12-22 9:53 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45274
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
Component|middle-end |tree-optimization
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-12-22 9:53 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-45274-4@http.gcc.gnu.org/bugzilla/>
2010-10-28 20:05 ` [Bug middle-end/45274] __restrict__ type qualifier does not work on pointers to bitfields pinskia at gcc dot gnu.org
2011-04-11 20:13 ` pinskia at gcc dot gnu.org
2021-12-22 9:53 ` [Bug tree-optimization/45274] " pinskia at gcc dot gnu.org
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).