Assignee: unassigned at gcc dot gnu.org
Reporter: bonzini at gnu dot org
Target Milestone: ---
Target: x86_64-pc-linux-gnu
Compiling QEMU's tests/unit/rcutorture.c file with GCC 12 causes an incorrect
optimization
Here is a reduced testcase:
extern void abort();
struct
Assignee: unassigned at gcc dot gnu.org
Reporter: bonzini at gnu dot org
Target Milestone: ---
Right now the only possibility to specify that combination
-fcf-protection=full, but this is not future proof; if other suboptions are
added later, they could be applied to code
at gcc dot gnu.org |bonzini at gnu dot org
Known to fail||7.3.1, 8.0.1
--- Comment #3 from Paolo Bonzini ---
Patch reverted due to PR84340.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84340
Paolo Bonzini changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84340
--- Comment #14 from Paolo Bonzini ---
I'll just revert the original PR84307 patch. Changing the fnspec has way too
many ramifications. PR84307 can either be fixed with an early UNPOISON
elimination pass, or delayed to GCC 9 where we can play
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84340
--- Comment #13 from Paolo Bonzini ---
Author: bonzini
Date: Tue Feb 13 13:03:22 2018
New Revision: 257625
URL: https://gcc.gnu.org/viewcvs?rev=257625=gcc=rev
Log:
gcc:
2018-02-13 Paolo Bonzini
PR sanitizer/84340
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84307
--- Comment #2 from Paolo Bonzini ---
Author: bonzini
Date: Tue Feb 13 13:03:22 2018
New Revision: 257625
URL: https://gcc.gnu.org/viewcvs?rev=257625=gcc=rev
Log:
gcc:
2018-02-13 Paolo Bonzini
PR sanitizer/84340
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84340
--- Comment #12 from Paolo Bonzini ---
No, I don't think computing a shadow memory address counts as memory
indirection.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84340
--- Comment #10 from Paolo Bonzini ---
> Note that we only instrument ASAN_CHECK for memory references. x=0 is not
> that
> case.
That depends... in use-after-scope-types-1.C there is inlining involved. With
my pass ordering change
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84340
--- Comment #7 from Paolo Bonzini ---
The problem is not the transformation from *ptr to x, the problem is that x=0
is later considered dead because ASAN_CHECK references are introduced too late.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84307
--- Comment #1 from Paolo Bonzini ---
Author: bonzini
Date: Mon Feb 12 12:47:56 2018
New Revision: 257585
URL: https://gcc.gnu.org/viewcvs?rev=257585=gcc=rev
Log:
gcc:
2018-02-12 Paolo Bonzini
PR sanitizer/84307
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84307
Paolo Bonzini changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
Assignee: unassigned at gcc dot gnu.org
Reporter: bonzini at gnu dot org
CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at
gcc dot gnu.org
Target Milestone
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80346
--- Comment #14 from Paolo Bonzini ---
And also treat it as undefined behavior and go straight to the else...
kidding, but not entirely!).
The main issue is that here we _are_ testing the overflow behavior of the
function, so we cannot pass sz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80346
--- Comment #12 from Paolo Bonzini ---
> So AFAICT, the warning for the first testcase is valid as well.
True, but isn't the maximum object size (2^63-1 aka PTRDIFF_MAX) as bogus as
2^64-1? We are using -1 which is a bit ugly but SIZE_MAX
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80346
--- Comment #8 from Paolo Bonzini ---
g_assertion_message_cmpnum is not declared anymore as noreturn since glib 2.38.
https://bugzilla.gnome.org/show_bug.cgi?id=692125 :-O
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80346
Paolo Bonzini changed:
What|Removed |Added
CC||bonzini at gnu dot org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49244
--- Comment #16 from Paolo Bonzini ---
> This also suggests there's an error in the current x86_64 kernel
> implementation
> as the kernel bitops are supposed to operate on machine word-size locations,
> so
> it should be using BTSQ not BTSL
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70079
--- Comment #2 from Paolo Bonzini ---
Yes, until combine there is the equivalent of
addl$512, %ecx;; 4
andl$-8, %ecx ;; 4.5
shrl$3, %ecx ;; 5
and combine is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68418
Paolo Bonzini changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
: target
Assignee: unassigned at gcc dot gnu.org
Reporter: bonzini at gnu dot org
Target Milestone: ---
int f(char *restrict a, const char *restrict b)
{
__builtin_memcpy(a, b, 512);
}
$ gcc f.c -O2 - -o f.s
includes the following code:
movq%rdi, %rcx
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65709
Paolo Bonzini changed:
What|Removed |Added
CC||bonzini at gnu dot org
--- Comment #20
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68418
--- Comment #2 from Paolo Bonzini ---
Author: bonzini
Date: Sat Dec 12 08:29:27 2015
New Revision: 231582
URL: https://gcc.gnu.org/viewcvs?rev=231582=gcc=rev
Log:
gcc:
PR sanitizer/68418
* c-family/c-ubsan.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66827
--- Comment #6 from Paolo Bonzini ---
If you really want to fix it, (-(1 << 19)) is the best.
The real fix would be to lobby the C/C++ committees so that left shift of a
negative value is unspecified behavior rather than undefined.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66827
Paolo Bonzini changed:
What|Removed |Added
CC||bonzini at gnu dot org
--- Comment #4
: sanitizer
Assignee: unassigned at gcc dot gnu.org
Reporter: bonzini at gnu dot org
CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
jakub at gcc dot gnu.org, kcc at gcc dot gnu.org
Target Milestone: ---
Left shifts into the sign
||2015-11-18
Assignee|unassigned at gcc dot gnu.org |bonzini at gnu dot org
Ever confirmed|0 |1
--- Comment #1 from Paolo Bonzini ---
I have a patch.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66790
--- Comment #35 from Paolo Bonzini ---
Comment on attachment 36377
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36377
Updated candidate patch
> + This problem determines which registers may be uninitialized. It first
> + assumes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66790
--- Comment #37 from Paolo Bonzini ---
Bernd is right that you have a missing 'else'.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66790
--- Comment #29 from Paolo Bonzini ---
> While getting familiar with DF problems, I noticed that LIVE's ignores
> the order of GENs and KILLs in basic blocks. In other words, the
> transfer function for: GEN(r1); KILL(r1) is currently the same
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66790
--- Comment #31 from Paolo Bonzini ---
Ah, I see now. I think you're right that the DF_REF_MUST_CLOBBER case should
also clear GEN in df_live_bb_local_compute.
However, regarding the "BTW" I am fairly sure now that df_live_bb_local_compute
and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66790
--- Comment #19 from Paolo Bonzini ---
LIVE provides live registers that MAY be initialized (are initialized on at
least one path). The comments are all wrong!
There's no code in GCC for must-initialized. Pierre's patch gets it right
(except
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66872
--- Comment #2 from Paolo Bonzini bonzini at gnu dot org ---
left shift of negative value is undefined behavior in C
It's not in any of GCC's intermediate representations, though.
Assignee: unassigned at gcc dot gnu.org
Reporter: bonzini at gnu dot org
Target Milestone: ---
This can save one or two instructions on some architectures. For example, when
compiling
int f(int x, int t)
{
return x ((1 t) - 1);
}
vs.
int f(int x, int t
Severity: normal
Priority: P3
Component: ipa
Assignee: unassigned at gcc dot gnu.org
Reporter: bonzini at gnu dot org
Target Milestone: ---
PR26854 is spending a lot of time in alias stmt walking
alias stmt walking : 272.52 (65%) (-O2)
alias stmt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66760
Paolo Bonzini bonzini at gnu dot org changed:
What|Removed |Added
Keywords||compile-time-hog
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26854
--- Comment #130 from Paolo Bonzini bonzini at gnu dot org ---
A late update...
all.i: with GCC 4.8.3 on a Xeon E5 v3 time is taken mostly by alias stmt
walking
alias stmt walking : 272.52 (65%) (-O2)
alias stmt walking : 116.06
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32394
Paolo Bonzini bonzini at gnu dot org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: bonzini at gnu dot org
Target Milestone: ---
This is caused by early SRA splitting elem's assignment into separate per-field
assignments.
struct x {
unsigned a : 6
: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: bonzini at gnu dot org
Version: gcc (GCC) 5.0.0 20150319 (Red Hat 5.0.0-0.21)
The following program does not warn with -Waggressive-loop-optimizations:
int a[4] = {1, 2, 3, 4};
int main()
{
int i, j
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50123
Paolo Bonzini bonzini at gnu dot org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39200
Paolo Bonzini bonzini at gnu dot org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21676
Bug 21676 depends on bug 39200, which changed state.
Bug 39200 Summary: ivopts slows down SciMark sparse matrix benchmark
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39200
What|Removed |Added
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39201
Bug 39201 depends on bug 39200, which changed state.
Bug 39200 Summary: ivopts slows down SciMark sparse matrix benchmark
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39200
What|Removed |Added
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28315
Paolo Bonzini bonzini at gnu dot org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56128
--- Comment #3 from Paolo Bonzini bonzini at gnu dot org 2013-01-28 13:36:36
UTC ---
--disable-target-libsanitizer should work:
# Handle --disable-component generically.
for dir in $configdirs $build_configdirs $target_configdirs ; do
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55597
Paolo Bonzini bonzini at gnu dot org changed:
What|Removed |Added
CC||stevenb.gcc
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55489
Paolo Bonzini bonzini at gnu dot org changed:
What|Removed |Added
Status|NEW |RESOLVED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55489
Bug #: 55489
Summary: [4.7 regression] insane PRE memory usage with PIE
(translate.i)
Classification: Unclassified
Product: gcc
Version: 4.7.2
Status:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55489
Paolo Bonzini bonzini at gnu dot org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55489
Paolo Bonzini bonzini at gnu dot org changed:
What|Removed |Added
Known to work|4.8.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55489
--- Comment #2 from Paolo Bonzini bonzini at gnu dot org 2012-11-27 20:27:09
UTC ---
Author: bonzini
Date: Tue Nov 27 20:26:57 2012
New Revision: 193867
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=193867
Log:
2012-11-27 Paolo
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55489
--- Comment #3 from Paolo Bonzini bonzini at gnu dot org 2012-11-27 20:29:24
UTC ---
Author: bonzini
Date: Tue Nov 27 20:29:15 2012
New Revision: 193868
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=193868
Log:
2012-11-27 Paolo
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55389
--- Comment #2 from Paolo Bonzini bonzini at gnu dot org 2012-11-19 13:05:51
UTC ---
Can you post the full log of a rm+make?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54206
--- Comment #7 from Paolo Bonzini bonzini at gnu dot org 2012-10-05 06:33:41
UTC ---
Building in srcdir usually works. Could it be as simple as this?
Index: Makefile.am
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27855
Paolo Bonzini bonzini at gnu dot org changed:
What|Removed |Added
Target Milestone|4.6.4 |4.7.2
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53336
--- Comment #4 from Paolo Bonzini bonzini at gnu dot org 2012-05-22 08:32:07
UTC ---
Author: bonzini
Date: Tue May 22 08:31:52 2012
New Revision: 187759
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=187759
Log:
gcc:
2012-05-16 Paolo
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53347
--- Comment #1 from Paolo Bonzini bonzini at gnu dot org 2012-05-15 09:56:59
UTC ---
The code in conforming_compare matches this comment with or without the
duplicate test:
(1) All comparison patterns are represented as
[(set (reg:CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53144
--- Comment #2 from Paolo Bonzini bonzini at gnu dot org 2012-04-28 06:19:31
UTC ---
In the case of PR53138 this was a preexisting bug in handling -(a b), made
more explicit by the new phi-opt conversion. Looking at vector-compare-1.c and
pass
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53144
Paolo Bonzini bonzini at gnu dot org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53138
Bug #: 53138
Summary: [4.7/4.8 Regression] spaceship operator miscompiled
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Keywords: wrong-code
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53138
Paolo Bonzini bonzini at gnu dot org changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53138
--- Comment #1 from Paolo Bonzini bonzini at gnu dot org 2012-04-27 12:18:03
UTC ---
Author: bonzini
Date: Fri Apr 27 12:17:50 2012
New Revision: 186904
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=186904
Log:
2012-04-27 Paolo Bonzini
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53087
Paolo Bonzini bonzini at gnu dot org changed:
What|Removed |Added
Status|NEW |ASSIGNED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53087
--- Comment #9 from Paolo Bonzini bonzini at gnu dot org 2012-04-25 20:00:57
UTC ---
The handling of this code sequence in fold-const changed back and forth many
times, and this is likely the reason why GCC 4.1 produced straight-line code
while
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49829
--- Comment #7 from Paolo Bonzini bonzini at gnu dot org 2012-01-19 08:59:02
UTC ---
The convenience library can be linked with -L.../.libs -lsupc++convenience
-lstdc++convenience98.
But it really looks like you attached the wrong patch?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49829
--- Comment #12 from Paolo Bonzini bonzini at gnu dot org 2012-01-20 07:52:26
UTC ---
(In reply to comment #10)
When there is not one convenience library, but three. Seems like my options
are:
1) combine the three convenience libraries
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49801
Paolo Bonzini bonzini at gnu dot org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51505
--- Comment #8 from Paolo Bonzini bonzini at gnu dot org 2012-01-18 08:58:33
UTC ---
I think you can just kill the note and call df_notes_rescan, can't you? (Sorry
for leaving this implicit in comment 4 and then forgetting about it yesterday).
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51505
--- Comment #10 from Paolo Bonzini bonzini at gnu dot org 2012-01-18 10:58:19
UTC ---
Not using df_notes_rescan looks like premature optimization to me...
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51505
--- Comment #6 from Paolo Bonzini bonzini at gnu dot org 2012-01-17 16:22:08
UTC ---
Yeah, perhaps you can make the code nicer by avoiding the nested loops:
for (use_rec = DF_INSN_EQ_USES (insn); *use_rec; use_rec
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49829
--- Comment #4 from Paolo Bonzini bonzini at gnu dot org 2012-01-03 13:06:50
UTC ---
You can just set enable_static=no early in libstdc++-v3/configure.ac. It will
still install libstdc++-v3.a, which is a bit ugly, but that's quite hard
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51447
--- Comment #8 from Paolo Bonzini bonzini at gnu dot org 2011-12-15 12:01:25
UTC ---
For ud_dce it's simplest to add/remove fake edges around it. For 4.8 it could
be worthwhile to try adding fake edges around all RTL passes (at least those
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51505
--- Comment #4 from Paolo Bonzini bonzini at gnu dot org 2011-12-13 19:34:25
UTC ---
No, it should be easy. Just look at the EQ_USES in df_kill_notes and, if one
EQ_USE refers to a dead pseudo, kill the REG_EQUAL or REG_EQUIV note.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51447
--- Comment #4 from Paolo Bonzini bonzini at gnu dot org 2011-12-07 13:48:42
UTC ---
The bug is that rbx is added to the EXIT_BLOCK uses:
Basic block 1 , prev 2, loop_depth 0, count 0, freq 0.
Predecessors:
;; bb 1 artificial_defs: { }
;; bb 1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51447
--- Comment #5 from Paolo Bonzini bonzini at gnu dot org 2011-12-07 14:04:04
UTC ---
Untested patch...
Index: df-problems.c
===
--- df-problems.c (revision 177688)
+++ df
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50935
--- Comment #5 from Paolo Bonzini bonzini at gnu dot org 2011-11-21 17:25:20
UTC ---
What's exactly the problem with gdb that requires disabling largefiles?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50991
--- Comment #9 from Paolo Bonzini bonzini at gnu dot org 2011-11-06 12:02:43
UTC ---
Yes, please commit the fix!
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50991
--- Comment #3 from Paolo Bonzini bonzini at gnu dot org 2011-11-04 14:23:40
UTC ---
I think the problem is that make clean is not removing libgcc_tm.stamp.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50991
--- Comment #5 from Paolo Bonzini bonzini at gnu dot org 2011-11-04 14:32:30
UTC ---
John didn't say that but you're right, because otherwise the move-if-change
would not have happened. John, can you attach libgcc/Makefile?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50982
--- Comment #6 from Paolo Bonzini bonzini at gnu dot org 2011-11-03 18:27:23
UTC ---
Paolo's suggestion probably was not well thought through.
Yes, it assumed that the patch would be tested by maintainers...
The patch looks good.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50448
--- Comment #4 from Paolo Bonzini bonzini at gnu dot org 2011-10-28 14:26:57
UTC ---
Can't you just test on x86_64-linux?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50696
Paolo Bonzini bonzini at gnu dot org changed:
What|Removed |Added
CC||bonzini at gnu dot
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49801
Paolo Bonzini bonzini at gnu dot org changed:
What|Removed |Added
CC||bonzini at gnu dot
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50573
--- Comment #5 from Paolo Bonzini bonzini at gnu dot org 2011-09-30 10:41:32
UTC ---
I'd just close it as wontfix. Perhaps we can fix the quoting problems, and
hope that autoconf removes duplicates another day.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50123
Bug #: 50123
Summary: cmpxchg generated for atomic and with zero/or with -1
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50047
--- Comment #1 from Paolo Bonzini bonzini at gnu dot org 2011-08-12 17:13:10
UTC ---
Author: bonzini
Date: Fri Aug 12 17:13:04 2011
New Revision: 177706
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=177706
Log:
2011-08-12 Paolo Bonzini
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49721
--- Comment #17 from Paolo Bonzini bonzini at gnu dot org 2011-08-03 06:32:42
UTC ---
H.J., I agree with what you write in comment 16. But unless we are sure that
the problematic composition will never be generated (e.g. by ivopts), we cannot
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48156
--- Comment #8 from Paolo Bonzini bonzini at gnu dot org 2011-03-18 16:24:25
UTC ---
I like the patch from comment 6.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38306
--- Comment #22 from Paolo Bonzini bonzini at gnu dot org 2011-02-21 07:55:35
UTC ---
What is the performance with 4.3 -O2? A regression that is limited to -O3 is
(a bit) less important since -O3 is still a mixing bag of optimizations that
might
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47782
Paolo Bonzini bonzini at gnu dot org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47225
--- Comment #34 from Paolo Bonzini bonzini at gnu dot org 2011-02-08 08:06:28
UTC ---
Iain,
the correct fix is to add -module to the LTO plugin LDFLAGS. This changes the
extension from .dylib to .so.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47225
--- Comment #36 from Paolo Bonzini bonzini at gnu dot org 2011-02-08 10:00:41
UTC ---
No, it should be added for all targets.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47225
--- Comment #24 from Paolo Bonzini bonzini at gnu dot org 2011-02-07 09:48:42
UTC ---
Please use LDFLAGS, not LIBADD.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47255
Paolo Bonzini bonzini at gnu dot org changed:
What|Removed |Added
CC||bonzini at gnu dot
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47435
--- Comment #2 from Paolo Bonzini bonzini at gnu dot org 2011-01-24 14:47:15
UTC ---
The code hardly makes any sense, so it's difficult to say which error message
makes more sense. I'll look at the regression.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47449
--- Comment #7 from Paolo Bonzini bonzini at gnu dot org 2011-01-24 23:45:01
UTC ---
Is this a regression?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47449
--- Comment #8 from Paolo Bonzini bonzini at gnu dot org 2011-01-24 23:47:10
UTC ---
Ah, [32] means 32-bit x86_64...
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47366
--- Comment #3 from Paolo Bonzini bonzini at gnu dot org 2011-01-20 13:12:02
UTC ---
Indeed, it never occurred to me but it should.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20385
--- Comment #10 from Paolo Bonzini bonzini at gnu dot org 2010-12-17 21:23:38
UTC ---
Author: bonzini
Date: Fri Dec 17 21:23:36 2010
New Revision: 167999
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=167999
Log:
gcc:
2010-12-17 Paolo
1 - 100 of 1258 matches
Mail list logo