--- Comment #3 from daney at gcc dot gnu dot org 2009-01-09 21:55 ---
Good, this code comes from the Linux kernel:
mm/backing-dev.c (set_bdi_congested())
Is the kernel at fault? If so I am sure Linus would like to hear about it.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3878
--- Comment #4 from pinskia at gcc dot gnu dot org 2009-01-09 21:56 ---
(In reply to comment #2)
> where the code is duplicated twice and both cases are constant.
Except it is not duplicated in jump threading. It would have been ok if it did
but it does not ...
Jump threading proved
--- Comment #5 from daney at gcc dot gnu dot org 2009-01-09 22:00 ---
You have to be able to do one of the original test case or this:
$ cat foo1.c
void baz(int v)
{
unsigned a;
a = (v == 1) ? 1 : 2;
if (__builtin_constant_p(a)) {
asm volatile
--- Comment #9 from rob1weld at aol dot com 2009-01-09 22:04 ---
(In reply to comment #8)
> The pic library is not used while compiling gcc so this warning is ok and
> not a bug.
Reopened.
That "bug" would be fixed it the "-fprofile-use" option were not given in
the directories that are
--- Comment #10 from pinskia at gcc dot gnu dot org 2009-01-09 22:07
---
>3. There is a "-Werror" to be fixed. Use: "i386.o-warn = -Wno-error"
I already mentioned this was really fixed in trunk already.
>5. The "C" and "Ada" Languages are being profiled (for the most part) but
the c
--- Comment #4 from rob1weld at aol dot com 2009-01-09 22:16 ---
(In reply to comment #3)
> You told the compiler to compile everything at the same time what do
> you expect to cause out of memory issues?
It could create temporary files (like qsort) and shrink the size of
the file (by o
--- Comment #5 from pinskia at gcc dot gnu dot org 2009-01-09 22:39 ---
That is the whole idea of http://gcc.gnu.org/wiki/LinkTimeOptimization :).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38788
--- Comment #6 from rguenth at gcc dot gnu dot org 2009-01-09 22:57 ---
Ok, I'm convinced. That jump-threading is really weird. But only because
__builtin_constant_p isn't a regular function that is executed on a path
of the CFG, it really is supposed to be evaluating all paths through
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
Summary|[4.4 Regression]|[4.4 Regression]
|__builtin_constant_p appears|__bu
--- Comment #7 from howarth at nitro dot med dot uc dot edu 2009-01-10
00:10 ---
Jerry,
It appears that the numerical values for all of the refinement table
entries are properly read. However for some reason the next line with the 'end'
statement gets lost. I have to duplicate this
--- Comment #1 from pault at gcc dot gnu dot org 2009-01-10 00:11 ---
Subject: Bug 38765
Author: pault
Date: Sat Jan 10 00:11:18 2009
New Revision: 143237
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=143237
Log:
2009-01-10 Paul Thomas
PR fortran/38765
* res
--- Comment #6 from pault at gcc dot gnu dot org 2009-01-10 00:15 ---
Subject: Bug 38763
Author: pault
Date: Sat Jan 10 00:15:37 2009
New Revision: 143238
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=143238
Log:
2009-01-10 Paul Thomas
PR fortran/38763
* tar
--- Comment #7 from pault at gcc dot gnu dot org 2009-01-10 00:21 ---
Fixed on trunk
Paul
--
pault at gcc dot gnu dot org changed:
What|Removed |Added
Summary
--- Comment #2 from pault at gcc dot gnu dot org 2009-01-10 00:21 ---
Fixed on trunk
Paul
--
pault at gcc dot gnu dot org changed:
What|Removed |Added
Summary
--- Comment #3 from zadeck at naturalbridge dot com 2009-01-10 01:57
---
Created an attachment (id=17068)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17068&action=view)
patch to cause df to verify after every patch
this is a combine bug. The df verification fails after combine
--- Comment #2 from rob1weld at aol dot com 2009-01-10 03:08 ---
OK, I'm going to propose:
# gdiff -Naur config.BACKUP2.guess config.guess
--- config.BACKUP2.guess2009-01-09 19:01:21.178338502 -0800
+++ config.guess2009-01-09 19:04:59.921763936 -0800
@@ -4,7 +4,7 @@
#
--- Comment #4 from rob1weld at aol dot com 2009-01-10 05:47 ---
Much further on in the build ...
...
# Early copyback; see "all" above for the rationale. The
# early copy is necessary so that the gcc -B options find
# the right startup files when linking shared libgcc.
/bin/sh ../../.
--- Comment #6 from rob1weld at aol dot com 2009-01-10 05:56 ---
(In reply to comment #1)
>> --enable-intermodule is not well tested at all. And second --combine is way
>> broken and really should be removed along with --enable-intermodule.
> ("one of Rob's comments")
>> That is the who
101 - 118 of 118 matches
Mail list logo
