I have now committed the attached patch.
This (r193204) breaks bootstrap on x86_64-apple-darwin10:
...
/opt/gcc/build_a/./prev-gcc/g++ -B/opt/gcc/build_a/./prev-gcc/
-B/opt/gcc/gcc4.8a/x86_64-apple-darwin10.8.0/bin/ -nostdinc++
On Tue, Nov 06, 2012 at 02:11:50PM -0800, H.J. Lu wrote:
On Tue, Nov 6, 2012 at 2:30 AM, Kirill Yukhin kirill.yuk...@gmail.com wrote:
Hello,
OK for mainline SVN, please commit.
Checked into GCC trunk: http://gcc.gnu.org/ml/gcc-cvs/2012-11/msg00176.html
Thanks, K
This caused:
On 11/06/12, Jason Merrillja...@redhat.com wrote:
Why three separate flags?
I thought extra flexibility might be wanted. On the other hand, *I* would
never turn off just one set. I expect a food fight over all flags. Also, if,
as seems reasonable, strict ANSI turns off all gnu
On 2012-11-06 06:37, Naveen H. S wrote:
+(define_insn iorbset_mem
+ [(set (match_operand:QI 0 rx_restricted_mem_operand =Q)
+ (ior:QI (match_operand:QI 1 rx_restricted_mem_operand %0)
+ (match_operand 2 const_int_operand Intso)))]
+ satisfies_constraint_Intso (operands[2])
From: Jan Hubicka hubi...@ucw.cz
Date: Tue, 6 Nov 2012 22:11:44 +0100
The attached patch fixes the testcase, so I comitted it as obvious. Hope it
will fix the bootstrap for you. I did not hit this because my bootstrap did
not
have graphite enabled due to lack of proper support libraries.
This patch fixes two stack alignment bugs in the split-stack support.
The first is that I managed to miscalculate the stack alignment in the
assembly code. I was treating that code as though it were a normal
function. That is wrong, because __morestack is actually called without
any stack
* testsuite/20_util/shared_ptr/cons/55123.cc: Remove duplicate
include.
Committed to trunk and 4.7
--- a/libstdc++-v3/testsuite/20_util/shared_ptr/cons/55123.cc
+++ b/libstdc++-v3/testsuite/20_util/shared_ptr/cons/55123.cc
@@ -22,8 +22,6 @@
// libstdc++/55123
-#include memory
I've merged trunk revision 193264 to the gccgo branch.
Ian
On 2012-11-05 19:44, Aldy Hernandez wrote:
There are 2 distinct compiler failures, which look like missed optimizations
which I will hopefully be tackling in stage2 (aka tomorrow).
FAIL: gcc.dg/tm/memopt-4.c scan-tree-dump-times tmedge tm_save.[0-9_]+ =
lala.x\\[55\\] 1
FAIL:
Thomas Schwinge, le Mon 05 Nov 2012 07:09:43 +0100, a écrit :
Samuel, is there any way you can unpack all Debian source packages on a
Debian machine, and run a recursive grep command (I can work out a
suitable regex) to see where removing the MACH or __MACH built-in
preprocessor macros might
Hi,
The problem here is the vector cost model causes some of the
functions not be vectorized even though we are scanning for the
explicit vectorization. This fixes the testcase by turning off the
cost model.
Thanks,
Andrew Pinski
2012-11-06 Andrew Pinski apin...@cavium.com
*
As asan/tsan functionality is getting into trunk, we need to set up
testings as soon as possible to avoid bitrot.
Kostya can probably shed some lights on the test case requirements,
and we can continue discussions on how to extend dejagnu to import
those tests.
thanks,
David
On Fri, Oct 12,
Committed as attached. Thanks everyone.
This (r193267) breaks bootstrap on x86_64-apple-darwin10:
...
g++ -c -g -DIN_GCC -fno-exceptions -fno-rtti -fasynchronous-unwind-tables
-W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute
-pedantic -Wno-long-long
On Tue, Nov 6, 2012 at 10:46 AM, Ian Lance Taylor i...@google.com wrote:
This patch to the Go compiler and library changes the size of the Go
type int to be the same as the size of a pointer. This means that on
x86_64 the size of int will be 64 bits. This matches the new behaviour
of the
On 11/6/12, Diego Novillo dnovi...@google.com wrote:
On Nov 5, 2012 Lawrence Crowl cr...@googlers.com wrote:
2012-11-05 Lawrence Crowl cr...@google.com
* compare_two_ftime_report_sets: New.
OK. Thanks.
Committed.
--
Lawrence Crowl
On Tue, Nov 6, 2012 at 4:32 PM, H.J. Lu hjl.to...@gmail.com wrote:
On Tue, Nov 6, 2012 at 10:46 AM, Ian Lance Taylor i...@google.com wrote:
This patch to the Go compiler and library changes the size of the Go
type int to be the same as the size of a pointer. This means that on
x86_64 the size
On Tue, Nov 6, 2012 at 4:29 PM, Dominique Dhumieres domi...@lps.ens.fr wrote:
Committed as attached. Thanks everyone.
This (r193267) breaks bootstrap on x86_64-apple-darwin10:
...
g++ -c -g -DIN_GCC -fno-exceptions -fno-rtti -fasynchronous-unwind-tables
-W -Wall -Wno-narrowing
On Tue, Nov 6, 2012 at 4:41 PM, Ian Lance Taylor i...@google.com wrote:
On Tue, Nov 6, 2012 at 4:32 PM, H.J. Lu hjl.to...@gmail.com wrote:
On Tue, Nov 6, 2012 at 10:46 AM, Ian Lance Taylor i...@google.com wrote:
This patch to the Go compiler and library changes the size of the Go
type int to
On Tue, Nov 6, 2012 at 4:51 PM, H.J. Lu hjl.to...@gmail.com wrote:
FAIL: ./tmp.go compilation, -O0 -g -fno-var-tracking-assignments
The Go library doesn't have proper support for x32 right now. I'm not
libgo works OK on x32 since x32 doesn't need much special treatment.
The above is the
I'm testing the enclosed patch on my end. Does it happen to work for you?
I am now past the previous error. Full answer tomorrow morning.
Thanks
Dominique
On Tue, 6 Nov 2012, Dominique Dhumieres wrote:
/opt/gcc/build_a/./prev-gcc/g++ -B/opt/gcc/build_a/./prev-gcc/
-B/opt/gcc/gcc4.8a/x86_64-apple-darwin10.8.0/bin/ -nostdinc++
-B/opt/gcc/build_a/prev-x86_64-apple-darwin10.8.0/libstdc++-v3/src/.libs
Yes, will do, but probably not so soon. Once I have some spare time to
prepare my case for this being useful to public.
Meanwhile, this patch is just for google-main and then I will port it
to google_4-7 and adds to the already existing functionality of
-mpatch-function-for-instrumentation.
On Tue, Nov 6, 2012 at 5:02 PM, Dominique Dhumieres domi...@lps.ens.fr wrote:
I'm testing the enclosed patch on my end. Does it happen to work for you?
I am now past the previous error. Full answer tomorrow morning.
Thanks
Dominique
I have committed the above fix as obvious. If there is
On Tue, Nov 6, 2012 at 5:01 PM, Ian Lance Taylor i...@google.com wrote:
On Tue, Nov 6, 2012 at 4:51 PM, H.J. Lu hjl.to...@gmail.com wrote:
FAIL: ./tmp.go compilation, -O0 -g -fno-var-tracking-assignments
The Go library doesn't have proper support for x32 right now. I'm not
libgo works OK
On Tue, Nov 6, 2012 at 11:18 PM, Jakub Jelinek ja...@redhat.com wrote:
On Tue, Nov 06, 2012 at 02:11:50PM -0800, H.J. Lu wrote:
On Tue, Nov 6, 2012 at 2:30 AM, Kirill Yukhin kirill.yuk...@gmail.com
wrote:
Hello,
OK for mainline SVN, please commit.
Checked into GCC trunk:
On Wed, Nov 7, 2012 at 8:03 AM, Uros Bizjak ubiz...@gmail.com wrote:
OK for mainline SVN, please commit.
Checked into GCC trunk:
http://gcc.gnu.org/ml/gcc-cvs/2012-11/msg00176.html
Thanks, K
This caused:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55224
Not only that, it also
201 - 226 of 226 matches
Mail list logo
