public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug tree-optimization/22000] New: Read from volatile member of struct is optimized away
@ 2005-06-10 13:59 rpedersen at atmel dot com
2005-06-10 14:00 ` [Bug tree-optimization/22000] " rpedersen at atmel dot com
` (14 more replies)
0 siblings, 15 replies; 16+ messages in thread
From: rpedersen at atmel dot com @ 2005-06-10 13:59 UTC (permalink / raw)
To: gcc-bugs
In the code below the read "(int)ptr->b;" gets optimized away.
It appears to be optimized away before the RTL stages, so I guess
it must be because of the tree optimalisation.
I think that the C standard says C that the "name" of variable
becomes an rvalue (the actual value) thus requires that the variable
is accessed.
Code:
struct test {
volatile int a;
volatile int b;
};
int main(int argc, char *argv[]){
struct test *ptr = (struct test *)0x10000000;
ptr->b = 10;
(int)ptr->b;
return 1;
}
--
Summary: Read from volatile member of struct is optimized away
Product: gcc
Version: 4.0.0
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: tree-optimization
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: rpedersen at atmel dot com
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: arm-unknown-elf
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22000
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Bug tree-optimization/22000] Read from volatile member of struct is optimized away
2005-06-10 13:59 [Bug tree-optimization/22000] New: Read from volatile member of struct is optimized away rpedersen at atmel dot com
@ 2005-06-10 14:00 ` rpedersen at atmel dot com
2005-06-10 14:07 ` [Bug tree-optimization/22000] [4.0 Regression] " pinskia at gcc dot gnu dot org
` (13 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: rpedersen at atmel dot com @ 2005-06-10 14:00 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From rpedersen at atmel dot com 2005-06-10 14:00 -------
Created an attachment (id=9059)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=9059&action=view)
Preprocessed testcase.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22000
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Bug tree-optimization/22000] [4.0 Regression] Read from volatile member of struct is optimized away
2005-06-10 13:59 [Bug tree-optimization/22000] New: Read from volatile member of struct is optimized away rpedersen at atmel dot com
2005-06-10 14:00 ` [Bug tree-optimization/22000] " rpedersen at atmel dot com
@ 2005-06-10 14:07 ` pinskia at gcc dot gnu dot org
2005-06-10 14:16 ` pinskia at gcc dot gnu dot org
` (12 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2005-06-10 14:07 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-06-10 14:07 -------
This works on the mainline, it might work on the 4.0.x branch too but I did not check yet.
--
What |Removed |Added
----------------------------------------------------------------------------
Severity|critical |normal
GCC build triplet|i686-pc-linux-gnu |
GCC host triplet|i686-pc-linux-gnu |
GCC target triplet|arm-unknown-elf |
Keywords| |wrong-code
Known to fail| |4.0.0
Known to work| |4.1.0 3.4.0
Summary|Read from volatile member of|[4.0 Regression] Read from
|struct is optimized away |volatile member of struct is
| |optimized away
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22000
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Bug tree-optimization/22000] [4.0 Regression] Read from volatile member of struct is optimized away
2005-06-10 13:59 [Bug tree-optimization/22000] New: Read from volatile member of struct is optimized away rpedersen at atmel dot com
2005-06-10 14:00 ` [Bug tree-optimization/22000] " rpedersen at atmel dot com
2005-06-10 14:07 ` [Bug tree-optimization/22000] [4.0 Regression] " pinskia at gcc dot gnu dot org
@ 2005-06-10 14:16 ` pinskia at gcc dot gnu dot org
2005-06-13 6:42 ` rpedersen at atmel dot com
` (11 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2005-06-10 14:16 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-06-10 14:16 -------
Still fails in 4.0.1.
Confirmed.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
Known to fail|4.0.0 |4.0.0 4.0.1
Last reconfirmed|0000-00-00 00:00:00 |2005-06-10 14:16:37
date| |
Target Milestone|--- |4.0.1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22000
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Bug tree-optimization/22000] [4.0 Regression] Read from volatile member of struct is optimized away
2005-06-10 13:59 [Bug tree-optimization/22000] New: Read from volatile member of struct is optimized away rpedersen at atmel dot com
` (2 preceding siblings ...)
2005-06-10 14:16 ` pinskia at gcc dot gnu dot org
@ 2005-06-13 6:42 ` rpedersen at atmel dot com
2005-06-13 11:17 ` schlie at comcast dot net
` (10 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: rpedersen at atmel dot com @ 2005-06-13 6:42 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From rpedersen at atmel dot com 2005-06-13 06:42 -------
Is it posible find out why it is woking in the mainline and generate
a patch for 4.0.0?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22000
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Bug tree-optimization/22000] [4.0 Regression] Read from volatile member of struct is optimized away
2005-06-10 13:59 [Bug tree-optimization/22000] New: Read from volatile member of struct is optimized away rpedersen at atmel dot com
` (3 preceding siblings ...)
2005-06-13 6:42 ` rpedersen at atmel dot com
@ 2005-06-13 11:17 ` schlie at comcast dot net
2005-06-13 11:56 ` rpedersen at atmel dot com
` (9 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: schlie at comcast dot net @ 2005-06-13 11:17 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From schlie at comcast dot net 2005-06-13 11:17 -------
(In reply to comment #0)
> I think that the C standard says C that the "name" of variable
> becomes an rvalue (the actual value) thus requires that the variable
> is accessed.
It actually says that accessing a volatile qualified object through a nonvolatile
qualified lvalue (as would be the case if referenced via a non-volatile qualified
cast expression) is implementation defined.
Personally, it seems more consistent to abide by the semantics specified
by a programmer's explicit cast expression, thereby if given:
int x, y;
const int *z;
x = (volatile int)y; // specifies a reference to a volatile int object.
z = &(const int)x; // specifies a reference to a const int object.
And correspondingly:
int x;
volatile int y;
const int z;
x = (int)y; // cast's away volatile (therefore may be optimized away),
// therefore if not desired, shouldn't be "cast away".
(int)z = x; // cast's away const (although may generate a run-time
// exception if referencing a READONLY allocated object),
// therefore if not desired, shouldn't be "cast away".
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22000
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Bug tree-optimization/22000] [4.0 Regression] Read from volatile member of struct is optimized away
2005-06-10 13:59 [Bug tree-optimization/22000] New: Read from volatile member of struct is optimized away rpedersen at atmel dot com
` (4 preceding siblings ...)
2005-06-13 11:17 ` schlie at comcast dot net
@ 2005-06-13 11:56 ` rpedersen at atmel dot com
2005-06-13 14:12 ` schlie at comcast dot net
` (8 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: rpedersen at atmel dot com @ 2005-06-13 11:56 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From rpedersen at atmel dot com 2005-06-13 11:56 -------
(In reply to comment #5)
> (In reply to comment #0)
> > I think that the C standard says C that the "name" of variable
> > becomes an rvalue (the actual value) thus requires that the variable
> > is accessed.
>
> It actually says that accessing a volatile qualified object through a
nonvolatile
> qualified lvalue (as would be the case if referenced via a non-volatile
qualified
> cast expression) is implementation defined.
>
If you are correct, the proposed testcase might be misleading.
Changing the expression for accessing the volatile member
of the struct to:
"(volatile int)ptr->b;"
or just:
"ptr->b;"
still leads to the access being optimized away.
> Personally, it seems more consistent to abide by the semantics specified
> by a programmer's explicit cast expression, thereby if given:
>
> int x, y;
> const int *z;
>
> x = (volatile int)y; // specifies a reference to a volatile int object.
>
> z = &(const int)x; // specifies a reference to a const int object.
>
> And correspondingly:
>
> int x;
> volatile int y;
> const int z;
>
> x = (int)y; // cast's away volatile (therefore may be optimized away),
> // therefore if not desired, shouldn't be "cast away".
>
> (int)z = x; // cast's away const (although may generate a run-time
> // exception if referencing a READONLY allocated object),
> // therefore if not desired, shouldn't be "cast away".
>
I agree with you on this.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22000
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Bug tree-optimization/22000] [4.0 Regression] Read from volatile member of struct is optimized away
2005-06-10 13:59 [Bug tree-optimization/22000] New: Read from volatile member of struct is optimized away rpedersen at atmel dot com
` (5 preceding siblings ...)
2005-06-13 11:56 ` rpedersen at atmel dot com
@ 2005-06-13 14:12 ` schlie at comcast dot net
2005-06-23 14:42 ` [Bug tree-optimization/22000] [4.0/4.1 " pinskia at gcc dot gnu dot org
` (7 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: schlie at comcast dot net @ 2005-06-13 14:12 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From schlie at comcast dot net 2005-06-13 14:12 -------
(In reply to comment #6)
> Changing the expression for accessing the volatile member
> of the struct to:
> "(volatile int)ptr->b;"
> or just:
> "ptr->b;"
> still leads to the access being optimized away.
Which seems like the real problem, as volatile access
sematics should clearly apply in both instances.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22000
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Bug tree-optimization/22000] [4.0/4.1 Regression] Read from volatile member of struct is optimized away
2005-06-10 13:59 [Bug tree-optimization/22000] New: Read from volatile member of struct is optimized away rpedersen at atmel dot com
` (6 preceding siblings ...)
2005-06-13 14:12 ` schlie at comcast dot net
@ 2005-06-23 14:42 ` pinskia at gcc dot gnu dot org
2005-06-23 15:11 ` mmitchel at gcc dot gnu dot org
` (6 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2005-06-23 14:42 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-06-23 14:42 -------
This looks like a latent bug on the mainline too, just harder to reproduce and here is a testcase:
struct test {
struct tt
{
volatile int a;
volatile int b;
} t;
};
int main(int argc, char *argv[]){
struct test *p = (struct test *)0x10000000;
struct tt *ptr = &p->t;
ptr->b = 10;
(int)ptr->b;
return 1;
}
--
What |Removed |Added
----------------------------------------------------------------------------
Summary|[4.0 Regression] Read from |[4.0/4.1 Regression] Read
|volatile member of struct is|from volatile member of
|optimized away |struct is optimized away
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22000
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Bug tree-optimization/22000] [4.0/4.1 Regression] Read from volatile member of struct is optimized away
2005-06-10 13:59 [Bug tree-optimization/22000] New: Read from volatile member of struct is optimized away rpedersen at atmel dot com
` (7 preceding siblings ...)
2005-06-23 14:42 ` [Bug tree-optimization/22000] [4.0/4.1 " pinskia at gcc dot gnu dot org
@ 2005-06-23 15:11 ` mmitchel at gcc dot gnu dot org
2005-06-23 15:28 ` mmitchel at gcc dot gnu dot org
` (5 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: mmitchel at gcc dot gnu dot org @ 2005-06-23 15:11 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From mmitchel at gcc dot gnu dot org 2005-06-23 15:11 -------
I somewhat suspect this hunk of code in c-typeck.c:build_component_ref:
if (TREE_THIS_VOLATILE (datum) || TREE_THIS_VOLATILE (subdatum))
TREE_THIS_VOLATILE (ref) = 1;
I don't see anything that sets TREE_SIDE_EFFECTS.
However, from tree.h:
If this bit is set in an expression, so is TREE_SIDE_EFFECTS. */
#define TREE_THIS_VOLATILE(NODE) ((NODE)->common.volatile_flag)
However, I'm having a hard time getting good connectivity back to my build
machine to experiment with this.
Joseph, any ideas about this?
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |joseph at codesourcery dot
| |com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22000
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Bug tree-optimization/22000] [4.0/4.1 Regression] Read from volatile member of struct is optimized away
2005-06-10 13:59 [Bug tree-optimization/22000] New: Read from volatile member of struct is optimized away rpedersen at atmel dot com
` (8 preceding siblings ...)
2005-06-23 15:11 ` mmitchel at gcc dot gnu dot org
@ 2005-06-23 15:28 ` mmitchel at gcc dot gnu dot org
2005-06-23 16:59 ` joseph at codesourcery dot com
` (4 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: mmitchel at gcc dot gnu dot org @ 2005-06-23 15:28 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From mmitchel at gcc dot gnu dot org 2005-06-23 15:28 -------
Hmm, no, TREE_SIDE_EFFECTS does seem to be getting set.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22000
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Bug tree-optimization/22000] [4.0/4.1 Regression] Read from volatile member of struct is optimized away
2005-06-10 13:59 [Bug tree-optimization/22000] New: Read from volatile member of struct is optimized away rpedersen at atmel dot com
` (9 preceding siblings ...)
2005-06-23 15:28 ` mmitchel at gcc dot gnu dot org
@ 2005-06-23 16:59 ` joseph at codesourcery dot com
2005-06-23 20:15 ` cvs-commit at gcc dot gnu dot org
` (3 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: joseph at codesourcery dot com @ 2005-06-23 16:59 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From joseph at codesourcery dot com 2005-06-23 16:59 -------
Subject: Re: [4.0/4.1 Regression] Read from
volatile member of struct is optimized away
On Thu, 23 Jun 2005, mmitchel at gcc dot gnu dot org wrote:
> I somewhat suspect this hunk of code in c-typeck.c:build_component_ref:
>
> if (TREE_THIS_VOLATILE (datum) || TREE_THIS_VOLATILE (subdatum))
> TREE_THIS_VOLATILE (ref) = 1;
>
> I don't see anything that sets TREE_SIDE_EFFECTS.
In general TREE_SIDE_EFFECTS is set by the low-level tree-building code in
tree.c (if set for the operands of a tree) so front ends need only change
it if the defaults are wrong.
> If this bit is set in an expression, so is TREE_SIDE_EFFECTS. */
> #define TREE_THIS_VOLATILE(NODE) ((NODE)->common.volatile_flag)
This does seem like something tree checking could usefully be added for.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22000
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Bug tree-optimization/22000] [4.0/4.1 Regression] Read from volatile member of struct is optimized away
2005-06-10 13:59 [Bug tree-optimization/22000] New: Read from volatile member of struct is optimized away rpedersen at atmel dot com
` (10 preceding siblings ...)
2005-06-23 16:59 ` joseph at codesourcery dot com
@ 2005-06-23 20:15 ` cvs-commit at gcc dot gnu dot org
2005-06-23 20:23 ` [Bug tree-optimization/22000] [4.1 " mmitchel at gcc dot gnu dot org
` (2 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: cvs-commit at gcc dot gnu dot org @ 2005-06-23 20:15 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-06-23 20:15 -------
Subject: Bug 22000
CVSROOT: /cvs/gcc
Module name: gcc
Branch: gcc-4_0-branch
Changes by: mmitchel@gcc.gnu.org 2005-06-23 20:15:29
Modified files:
gcc : ChangeLog tree-ssa-operands.c
Log message:
PR 22000
* tree-ssa-operands.c (get_expr_operands): Check the volatility of
the FIELD_DECL and set s_ann->has_volatile_ops accordingly.
Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=2.7592.2.290&r2=2.7592.2.291
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/tree-ssa-operands.c.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=2.63&r2=2.63.2.1
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22000
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Bug tree-optimization/22000] [4.1 Regression] Read from volatile member of struct is optimized away
2005-06-10 13:59 [Bug tree-optimization/22000] New: Read from volatile member of struct is optimized away rpedersen at atmel dot com
` (11 preceding siblings ...)
2005-06-23 20:15 ` cvs-commit at gcc dot gnu dot org
@ 2005-06-23 20:23 ` mmitchel at gcc dot gnu dot org
2005-06-24 3:38 ` cvs-commit at gcc dot gnu dot org
2005-06-24 3:40 ` mmitchel at gcc dot gnu dot org
14 siblings, 0 replies; 16+ messages in thread
From: mmitchel at gcc dot gnu dot org @ 2005-06-23 20:23 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From mmitchel at gcc dot gnu dot org 2005-06-23 20:23 -------
Fixed in 4.0.1.
--
What |Removed |Added
----------------------------------------------------------------------------
Summary|[4.0/4.1 Regression] Read |[4.1 Regression] Read from
|from volatile member of |volatile member of struct is
|struct is optimized away |optimized away
Target Milestone|4.0.1 |4.1.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22000
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Bug tree-optimization/22000] [4.1 Regression] Read from volatile member of struct is optimized away
2005-06-10 13:59 [Bug tree-optimization/22000] New: Read from volatile member of struct is optimized away rpedersen at atmel dot com
` (12 preceding siblings ...)
2005-06-23 20:23 ` [Bug tree-optimization/22000] [4.1 " mmitchel at gcc dot gnu dot org
@ 2005-06-24 3:38 ` cvs-commit at gcc dot gnu dot org
2005-06-24 3:40 ` mmitchel at gcc dot gnu dot org
14 siblings, 0 replies; 16+ messages in thread
From: cvs-commit at gcc dot gnu dot org @ 2005-06-24 3:38 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-06-24 03:38 -------
Subject: Bug 22000
CVSROOT: /cvs/gcc
Module name: gcc
Changes by: mmitchel@gcc.gnu.org 2005-06-24 03:38:06
Modified files:
gcc : ChangeLog tree-ssa-operands.c
Log message:
PR 22000
* tree-ssa-operands.c (get_expr_operands): Check the volatility of
the FIELD_DECL and set s_ann->has_volatile_ops accordingly.
Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&r1=2.9215&r2=2.9216
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/tree-ssa-operands.c.diff?cvsroot=gcc&r1=2.87&r2=2.88
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22000
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Bug tree-optimization/22000] [4.1 Regression] Read from volatile member of struct is optimized away
2005-06-10 13:59 [Bug tree-optimization/22000] New: Read from volatile member of struct is optimized away rpedersen at atmel dot com
` (13 preceding siblings ...)
2005-06-24 3:38 ` cvs-commit at gcc dot gnu dot org
@ 2005-06-24 3:40 ` mmitchel at gcc dot gnu dot org
14 siblings, 0 replies; 16+ messages in thread
From: mmitchel at gcc dot gnu dot org @ 2005-06-24 3:40 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From mmitchel at gcc dot gnu dot org 2005-06-24 03:40 -------
Fixed in 4.0.1.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22000
^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2005-06-24 3:40 UTC | newest]
Thread overview: 16+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-06-10 13:59 [Bug tree-optimization/22000] New: Read from volatile member of struct is optimized away rpedersen at atmel dot com
2005-06-10 14:00 ` [Bug tree-optimization/22000] " rpedersen at atmel dot com
2005-06-10 14:07 ` [Bug tree-optimization/22000] [4.0 Regression] " pinskia at gcc dot gnu dot org
2005-06-10 14:16 ` pinskia at gcc dot gnu dot org
2005-06-13 6:42 ` rpedersen at atmel dot com
2005-06-13 11:17 ` schlie at comcast dot net
2005-06-13 11:56 ` rpedersen at atmel dot com
2005-06-13 14:12 ` schlie at comcast dot net
2005-06-23 14:42 ` [Bug tree-optimization/22000] [4.0/4.1 " pinskia at gcc dot gnu dot org
2005-06-23 15:11 ` mmitchel at gcc dot gnu dot org
2005-06-23 15:28 ` mmitchel at gcc dot gnu dot org
2005-06-23 16:59 ` joseph at codesourcery dot com
2005-06-23 20:15 ` cvs-commit at gcc dot gnu dot org
2005-06-23 20:23 ` [Bug tree-optimization/22000] [4.1 " mmitchel at gcc dot gnu dot org
2005-06-24 3:38 ` cvs-commit at gcc dot gnu dot org
2005-06-24 3:40 ` mmitchel at gcc dot gnu dot 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).