public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/3506] weird behaviour when incrementing volatile ints
[not found] <20010701090600.3506.89949-quiet@bugs.debian.org>
@ 2005-05-15 13:33 ` pinskia at gcc dot gnu dot org
2005-05-15 13:34 ` pinskia at gcc dot gnu dot org
` (4 subsequent siblings)
5 siblings, 0 replies; 11+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2005-05-15 13:33 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-15 13:33 -------
Reopen to ...
--
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3506
^ permalink raw reply [flat|nested] 11+ messages in thread* [Bug target/3506] weird behaviour when incrementing volatile ints
[not found] <20010701090600.3506.89949-quiet@bugs.debian.org>
2005-05-15 13:33 ` [Bug target/3506] weird behaviour when incrementing volatile ints pinskia at gcc dot gnu dot org
@ 2005-05-15 13:34 ` pinskia at gcc dot gnu dot org
2005-05-15 13:34 ` pinskia at gcc dot gnu dot org
` (3 subsequent siblings)
5 siblings, 0 replies; 11+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2005-05-15 13:34 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-15 13:34 -------
*** Bug 21580 has been marked as a duplicate of this bug. ***
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |mrd at alkemio dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3506
^ permalink raw reply [flat|nested] 11+ messages in thread* [Bug target/3506] weird behaviour when incrementing volatile ints
[not found] <20010701090600.3506.89949-quiet@bugs.debian.org>
2005-05-15 13:33 ` [Bug target/3506] weird behaviour when incrementing volatile ints pinskia at gcc dot gnu dot org
2005-05-15 13:34 ` pinskia at gcc dot gnu dot org
@ 2005-05-15 13:34 ` pinskia at gcc dot gnu dot org
2005-05-16 22:34 ` mrd at alkemio dot org
` (2 subsequent siblings)
5 siblings, 0 replies; 11+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2005-05-15 13:34 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-15 13:33 -------
Mark as invalid.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3506
^ permalink raw reply [flat|nested] 11+ messages in thread* [Bug target/3506] weird behaviour when incrementing volatile ints
[not found] <20010701090600.3506.89949-quiet@bugs.debian.org>
` (2 preceding siblings ...)
2005-05-15 13:34 ` pinskia at gcc dot gnu dot org
@ 2005-05-16 22:34 ` mrd at alkemio dot org
2005-05-16 22:57 ` pinskia at gcc dot gnu dot org
2005-05-17 0:33 ` mrd at alkemio dot org
5 siblings, 0 replies; 11+ messages in thread
From: mrd at alkemio dot org @ 2005-05-16 22:34 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From mrd at alkemio dot org 2005-05-16 22:34 -------
(In reply to comment #5)
> Mark as invalid.
Why?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3506
^ permalink raw reply [flat|nested] 11+ messages in thread* [Bug target/3506] weird behaviour when incrementing volatile ints
[not found] <20010701090600.3506.89949-quiet@bugs.debian.org>
` (3 preceding siblings ...)
2005-05-16 22:34 ` mrd at alkemio dot org
@ 2005-05-16 22:57 ` pinskia at gcc dot gnu dot org
2005-05-17 0:33 ` mrd at alkemio dot org
5 siblings, 0 replies; 11+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2005-05-16 22:57 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-16 22:57 -------
(In reply to comment #7)
> (In reply to comment #5)
> > Mark as invalid.
>
> Why?
Did you read comment #1.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3506
^ permalink raw reply [flat|nested] 11+ messages in thread* [Bug target/3506] weird behaviour when incrementing volatile ints
[not found] <20010701090600.3506.89949-quiet@bugs.debian.org>
` (4 preceding siblings ...)
2005-05-16 22:57 ` pinskia at gcc dot gnu dot org
@ 2005-05-17 0:33 ` mrd at alkemio dot org
5 siblings, 0 replies; 11+ messages in thread
From: mrd at alkemio dot org @ 2005-05-17 0:33 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From mrd at alkemio dot org 2005-05-17 00:33 -------
(In reply to comment #8)
> Did you read comment #1.
Yes, but it's not clear.
> GCC doesn't know what constitutes a reference to a volatile memory
Is this to say the GCC developers believe the C language's definition of
"volatile" is ambiguous, or that there are situations where "incl x" is
operationally distinct from "movl x, %eax; incl %eax; movl %eax, x" when x is
volatile?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3506
^ permalink raw reply [flat|nested] 11+ messages in thread
[parent not found: <bug-3506-4828@http.gcc.gnu.org/bugzilla/>]
[parent not found: <bug-3506-4@http.gcc.gnu.org/bugzilla/>]
end of thread, other threads:[~2023-02-09 18:11 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <20010701090600.3506.89949-quiet@bugs.debian.org>
2005-05-15 13:33 ` [Bug target/3506] weird behaviour when incrementing volatile ints pinskia at gcc dot gnu dot org
2005-05-15 13:34 ` pinskia at gcc dot gnu dot org
2005-05-15 13:34 ` pinskia at gcc dot gnu dot org
2005-05-16 22:34 ` mrd at alkemio dot org
2005-05-16 22:57 ` pinskia at gcc dot gnu dot org
2005-05-17 0:33 ` mrd at alkemio dot org
[not found] <bug-3506-4828@http.gcc.gnu.org/bugzilla/>
2007-08-18 0:06 ` pinskia at gcc dot gnu dot org
2007-08-18 0:13 ` pinskia at gcc dot gnu dot org
2008-12-28 2:49 ` pinskia at gcc dot gnu dot org
[not found] <bug-3506-4@http.gcc.gnu.org/bugzilla/>
2020-07-27 2:06 ` pinskia at gcc dot gnu.org
2023-02-09 18:11 ` 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).