--- Comment #29 from mmitchel at gcc dot gnu dot org 2010-08-31 17:41
---
Jason --
I can't argue with that as a literal reading of the standard, but is there any
reason why the standard doesn't allow const float variables in (not necessarily
integral) constant expressions
--- Comment #10 from mmitchel at gcc dot gnu dot org 2010-08-17 17:50
---
The problem with -Wuninitialized might be the same problem I've been
sermonizing about for years -- we're trying to issue sensible warnings from our
optimizers, which means that as the optimizers are
--- Comment #4 from mmitchel at gcc dot gnu dot org 2010-08-17 14:41
---
I have no object to the FE removing trivial code if it can do so -- but I also
think that the middle-end should be able to deduce that a function is pure
later in the process and eliminate it then.
I don
--- Comment #13 from mmitchel at gcc dot gnu dot org 2010-04-20 20:43
---
I think this optimization is valuable in some cases, so I think this is a
question of defaults, rather than of behavior per se. While it may be useful
for some security-related applications not to eliminate the
--- Comment #47 from mmitchel at gcc dot gnu dot org 2010-03-21 16:47
---
Closed at request of submitter.
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #22 from mmitchel at gcc dot gnu dot org 2010-02-28 17:08
---
Subject: Bug 42748
Author: mmitchel
Date: Sun Feb 28 17:07:54 2010
New Revision: 157124
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=157124
Log:
2010-02-27 Mark Mitchell
PR c
--- Comment #6 from mmitchel at gcc dot gnu dot org 2010-02-24 16:28
---
Ralf --
I think the key question here is whether it is possible to build/install a new
version of GCC, getting the same directory layout as was the default in
previous versions. It's OK if it takes command
--- Comment #4 from mmitchel at gcc dot gnu dot org 2010-02-22 23:23
---
I don't think this should be P1, as getting the old behavior is apparently
doable by hand, but I'm a big fan of backwards-compatibility and if the GCS
haven't been updated then I think that GCC (a
--- Comment #18 from mmitchel at gcc dot gnu dot org 2010-02-18 15:13
---
Paolo --
I think libsupc++ is just as much a "system library" as libstdc++. It doesn't
have an ISO-standard API, of course, but that's not the point; it's just as
much a part of the
--- Comment #16 from mmitchel at gcc dot gnu dot org 2010-02-18 04:40
---
Paolo --
I don't understand why all libstdc++ headers should not have #pragma GCC
system_header in them. Would you please explain that?
I think there's a semantic hair that we could split about wh
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42431
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42749
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P5
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42143
--- Comment #10 from mmitchel at gcc dot gnu dot org 2010-02-17 17:51
---
IIUC, this is not a regression.
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43093
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43079
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43066
--- Comment #3 from mmitchel at gcc dot gnu dot org 2010-02-17 17:42
---
Richard, is this fixed now?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43074
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43087
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43101
--- Comment #3 from mmitchel at gcc dot gnu dot org 2010-02-17 17:38
---
I think we need to understand Steven's comment that ipa-struct-reorg is
"broken". This pass isn't on by default, AFAICT, so that decreases it's risk.
But, if it's broken-by-design
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43076
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43069
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P5
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43055
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P5
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42851
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42839
--- Comment #5 from mmitchel at gcc dot gnu dot org 2010-02-17 17:27
---
Do we have any evidence that this is actually a regression? If this test has
never worked on IA64/HPPA, then this is not a regression. It should then be
XFAIL'd on those platforms, with this PR left
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42505
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42502
--- Comment #44 from mmitchel at gcc dot gnu dot org 2010-02-17 17:20
---
As I understand it, this is an Alpha-specific problem. It may have an
Alpha-independent solution, but only users on Alpha will be affected. So, I've
downgraded this to P5.
--
mmitchel at gcc dot gnu do
--- Comment #13 from mmitchel at gcc dot gnu dot org 2010-02-17 17:15
---
I reluctantly agree with Ian's comment in:
http://gcc.gnu.org/ml/gcc/2010-01/msg00332.html
that:
"I think it would be troubling if a gcc release required a very new
binutils release on a popular pla
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27016
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43097
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P5
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43096
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43083
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43070
--- Comment #1 from mmitchel at gcc dot gnu dot org 2010-02-17 16:58
---
I take the P1 setting back; I failed to recognize the use of
-fgraphite-identity. As long as that's not a default setting, I don't think
problems there should be P1.
--
mmitchel at gcc dot gnu dot o
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43065
--- Comment #7 from mmitchel at gcc dot gnu dot org 2010-02-17 16:56
---
I think this is a critical problem. If var-tracking is causing factor-of-N
increases in memory usage, then we need an algorithmic change that prevents
that, even if that means inferior debug information. We
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42886
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42729
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42648
--- Comment #22 from mmitchel at gcc dot gnu dot org 2010-02-17 16:52
---
I don't think we really know enough yet to understand whether this is a bug, or
if it is a bug, where the bug might lie. So, we certainly can't make it P1,
ignoring even the fact that this test is
--- Comment #31 from mmitchel at gcc dot gnu dot org 2010-02-17 16:49
---
I still have no idea what this PR is about. Someone needs to make a clear
statement of what they believe the ABI to be. There are some simple questions:
* Can we expect that the stack is 16-byte aligned, or
--- Comment #6 from mmitchel at gcc dot gnu dot org 2010-01-25 03:16
---
Fixed.
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Status|NEW
--- Comment #5 from mmitchel at gcc dot gnu dot org 2010-01-25 03:14
---
Subject: Bug 42748
Author: mmitchel
Date: Mon Jan 25 03:14:25 2010
New Revision: 156202
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=156202
Log:
PR c++/42748
* config/a
--- Comment #8 from mmitchel at gcc dot gnu dot org 2010-01-15 03:26
---
Ramana --
If I'm reading the log correctly for PR36633 the change that Jason made there
didn't actually fix the bug; it was just a cleanup. He commented that
something else had changed which made the b
--- Comment #4 from mmitchel at gcc dot gnu dot org 2010-01-15 00:17
---
OK, I will fix this one.
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #2 from mmitchel at gcc dot gnu dot org 2010-01-14 19:22
---
Paolo --
I think that the warning is accurate; the mangling of va_list has indeed
changed on ARM in GCC 4.4 in order to conform to the ARM ABI specifications.
There is an option to turn off warnings about PSABI
--- Comment #12 from mmitchel at gcc dot gnu dot org 2009-09-01 13:54
---
I think the question is whether the use of __optimize__ is in a standard Qt
release. If it is, then I'm quite concerned; it's bad if GCC 4.4.2 can't build
Qt/KDE.
(TBH, I'm concerned anyhow
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41153
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41038
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40808
--- Comment #32 from mmitchel at gcc dot gnu dot org 2009-08-31 21:48
---
Can anyone confirm that this is fixed?
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #4 from mmitchel at gcc dot gnu dot org 2009-08-31 21:47
---
HJ, this doesn't make sense.
Either we can assume 16-byte stack alignment, or we can't. Which is it?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41156
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P5
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40775
--- Comment #9 from mmitchel at gcc dot gnu dot org 2009-08-24 16:10
---
I think maybe it's time for me to get a brain transplant. I had totally
forgotten the previous conversation, and read through this entire issue
yesterday, and then spent some time thinking about the issue
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40965
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P5
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41139
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41086
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41043
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40778
--- Comment #3 from mmitchel at gcc dot gnu dot org 2009-08-24 01:04
---
This may very well indicate that PCH is totally busted in 4.5; we need to
figure that out.
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #7 from mmitchel at gcc dot gnu dot org 2009-08-24 01:03
---
I think we should leave this warning out of -Wall. There's a lot of legacy C
code that may do this kind of stuff. In C++, it's always been invalid, and
there's more of an expectation of structured
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P5
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41112
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41020
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40022
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30210
--- Comment #11 from mmitchel at gcc dot gnu dot org 2009-05-05 16:11
---
Richard, can this be closed now?
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #14 from mmitchel at gcc dot gnu dot org 2009-05-05 16:10
---
Janis, is this still an issue?
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #12 from mmitchel at gcc dot gnu dot org 2009-05-05 16:09
---
HP, is this still a problem?
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39666
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40021
--- Comment #8 from mmitchel at gcc dot gnu dot org 2009-05-05 16:00
---
Steve --
Is there still an issue here?
-- Mark
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39960
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39959
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39886
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39862
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39856
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40026
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39987
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39978
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39976
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39974
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39958
--- Comment #12 from mmitchel at gcc dot gnu dot org 2009-05-05 15:48
---
Yes, we've been discussing the interaction between attributes and the type
system for at least a decade. :-) In type-theoretic terms, the address of a
packed int has type pointer-to-packed-int, not point
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39898
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P2
Summary|[4.3/4.4/4.5 regression] CSE|[4.3/4.4/4.5
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P2
Summary|[4.4/4.5 Regression]|[4.4/4.5
--- Comment #16 from mmitchel at gcc dot gnu dot org 2009-05-05 15:13
---
Jules, is the ARM GNU/Linux build still broken?
David, how about AIX?
Thanks,
-- Mark
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: mmitchel at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39801
--- Comment #24 from mmitchel at gcc dot gnu dot org 2009-02-21 22:26
---
The problem isn't the database schema; it's keeping it up to date.
I'm not actively working on this issue any more, so I've unassigned myself.
--
mmitchel at gcc dot gnu dot org chang
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39204
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39202
--- Comment #4 from mmitchel at gcc dot gnu dot org 2009-02-17 02:53
---
The key question is whether the bogus warning could indicate a potential for
miscompilation. If it's "just" a bogus warning, then it's going to annoy and
confuse people, but not result in t
--- Comment #7 from mmitchel at gcc dot gnu dot org 2009-02-13 16:41
---
In that case, this isn't a high-priority bug. That doesn't mean that it can't
be fixed before 4.4; that's up to the x86 maintainers. But, it shouldn't block
the release.
--
mmitch
--- Comment #5 from mmitchel at gcc dot gnu dot org 2009-02-11 01:45
---
Is this a regression?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39082
--- Comment #17 from mmitchel at gcc dot gnu dot org 2009-02-09 22:53
---
The patch to remove addr2name.awk has now been committed to mainline. I am not
sure what else, if anything, remains on this PR.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=5303
--- Comment #16 from mmitchel at gcc dot gnu dot org 2009-02-09 22:45
---
Patch to remove addr2name.awk now available here:
http://gcc.gnu.org/ml/java-patches/2009-q1/msg00013.html
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=5303
1 - 100 of 4516 matches
Mail list logo