Diego,
Testing w/ ubuntu lucid native bootstrap + check (C/C++), with --with-pic
and numerous other flags, looking good.
OK for google/main (assuming tests succeed)?
chris
--
[libgcc/ChangeLog.google-main]
2011-05-04 Chris Demetriou
Backport from trunk r173391:
2011-05-04 C
On Wed, May 4, 2011 at 06:19, Jerry DeLisle wrote:
> Hi Folks,
>
> This patch fixes the latest 'round' of test cases from Thomas. The patch
> adjusts the count of digits before the decimal point by one where w>0 and
> d==0. The patch also consolidates some of the code as a clean up.
>
> Regressi
> "Jakub" == Jakub Jelinek writes:
Tom> Should DW_OP_bra be restricted to integral types? Several other opcodes
Jakub> Yes. If you want to test other types, just compare them against 0
Jakub> using DW_OP_ne etc.
Great, thanks.
Tom> Currently, the comparison operators are all defined as p
This patch adds a new streamer hook to populate the streamer cache
with common nodes.
The nodes we populate for GIMPLE in lto_get_common_nodes is not
sufficient for C++, unsurprisingly.
The patch fixes these regressions in pph.exp:
FAIL: g++.dg/pph/p1stdlib.cc -fpph-map=pph.map -I. (test for e
On 05/04/2011 09:12 PM, Joseph S. Myers wrote:
-# hpux11 in 64bit mode has libraries in a weird place. Arrange to find
-# them automatically.
-
-# The Solaris /usr/ucb/cc compiler does not appear to work.
Ok.
Paolo
Committed the attached patch to google/main. Will send a patch for trunk soon.
On Thu, Apr 28, 2011 at 10:03 PM, Xinliang David Li wrote:
> Please add regression test cases for the feature. Address the comments
> when available. Ok for google/main.
>
> Thanks,
>
> David
>
> On Thu, Apr 28, 2011
> Following recent discussions of variable_size, this patch stops the C
> front end from using the global pending_sizes list, instead using the
> existing grokdeclarator support for tracking size expressions in the
> one case where pending sizes were still needed. c_variable_size is
> replaced by
Once or twice a year some regression results from changed I/O
in libgfortran, such that some existing test-case starts
calling libgfortran/io/unix.c:raw_truncate, which on
limited-I/O-bare-iron targets will emit "required ftruncate or
chsize support not present" and fail. After a while, I get to
i
On Wed, May 4, 2011 at 15:50, Chris Demetriou wrote:
> 2011-05-04 Chris Demetriou
>
> Backport from trunk r173391:
> 2011-05-04 Chris Demetriou
>
> * config/i386/morestack.S (__i686.get_pc_thunk.bx): Rename to...
> (__x86.get_pc_thunk.bx): ...this.
> (__mo
On Wed, May 4, 2011 at 15:35, Sriraman Tallam wrote:
> * tree-pass.h (pass_tree_convert_builtin_dispatch): New pass.
> (pass_ipa_multiversion_dispatch): New pass.
> * builtin-types.def (BT_PTR_FN_INT): New pointer type.
> (BT_FN_INT_PTR_FN_INT_PTR_PTR_VAR): New functio
I submitted the patch.
Thanks,
-Sri.
On Wed, May 4, 2011 at 3:13 PM, Diego Novillo wrote:
> On Wed, May 4, 2011 at 15:35, Sriraman Tallam wrote:
>
>> * tree-pass.h (pass_tree_convert_builtin_dispatch): New pass.
>> (pass_ipa_multiversion_dispatch): New pass.
>> * builtin-ty
>
> I can think of some more-or-less obvious high-level forms, one would
> for example simply stick a new DISPATCH tree into gimple_call_fn
> (similar to how we can have OBJ_TYPE_REF there), the DISPATCH
> tree would be of variable length, first operand the selector function
> and further operands
The problem was that fixed_type_or_null was looking closely at things
that aren't meant to be looked at closely when we're in templates,
namely a COMPONENT_REF where operand 1 is an IDENTIFIER. In a template
we're going to discard the conversion anyway once we decide it's OK, so
we might as we
Hi,
this patch makes inliner more selective about when to test can_inline_edge_p
and when to reset edge caches. The first appears quite hot in Mozilla LTO
build profiles
now, since we used to do way too many resets even when not neccesary.
After inlining function A to B, we need:
1) reset edge
> Well, I disagree. STATEMENT_LISTs are just another kind of thing you
> encounter in an expression; if a caller wants special handling, they can
> arrange for it.
But you're unilaterally choosing one special handling (copying) among several
ones (copying, not copying, aborting) just because of
Hi,
Marc kindly contributed the below rewrite of std::ratio_add (and
ratio_less), algorithmically derived from the macro __udiv_qrnnd_c in
gcc's longlong.h, which amounts to the best behavior in terms of
accepted inputs: a pair of std::ratio is *never* rejected unless the
resulting std::ratio
Is this patch ok for trunk?
Allowing relative path in -fprofile-generate= is very useful when
running the program remotely -- the profile data will be just dumped
in the dir relative to the working dir in the remote machine. Using
GCOV_PREFIX_STRIP can workaround the problem, but it is not always
On May 4, 2011, at 11:46 AM, Joseph S. Myers wrote:
> I explicitly approve trailing whitespace removal from all .texi files and
> other documentation not imported from upstream sources outside of GCC
> (subject to handling generated files properly, so any changes to tm.texi
> should be done by c
On May 4, 2011, at 11:40 AM, Gerald Pfeifer wrote:
> Documentation may be a bit more relaxed, and if you have one doc
> maintainer approve and the other abstain that may be more boring
> that you might hope for. :-)
Actually, I was aiming for a global person to ack gcc/*... This could be less
bo
On May 4, 2011, at 9:38 AM, Joseph S. Myers wrote:
> Following recent discussions of variable_size, this patch stops the C
> front end from using the global pending_sizes list
> Are the ObjC changes OK to commit?
Ok. Don't forget about Objective-C++. It isn't the default.
The last remaining uses of build_function_type in the ObjC/C++ frontends
comes from this pattern:
tree method_param_types =
get_arg_type_list (method_prototype, METHOD_REF, super_flag);
tree ftype = build_function_type (ret_type, method_param_types);
To eliminate this, I made the followin
This patch to the Go frontend uses the backend interface for slice
types. Bootstrapped and ran Go testsuite on x86_64-unknown-linux-gnu.
Committed to mainline.
Ian
diff -r 37dae2a9c21b go/gogo-tree.cc
--- a/go/gogo-tree.cc Wed May 04 08:38:47 2011 -0700
+++ b/go/gogo-tree.cc Wed May 04 22:18:22
This patch improves cross module option mismatch handling in LIPO mode -- will
be commited to google/main.
1) Remove duplicates in the option list before comparison;
2) Force module incompatiblity when two modules disagree in -fexceptions
setting. In LIPO mode, when option mismatch is discovered
This patch does the first minor steps towards TR 29113: It accepts the
OPTIONAL attribute in procedures with C binding. As gfortran already
passes absent arguments a NULL pointer, there is no changed needed,
except in the diagnostics part. Additionally, it is a feature also
supported by other c
Before, scalar coarrays were not supported in the coindex intrinsics as
they did not have - on tree level - cobounds attached to them. This
patch adds them.
Additionally, it fixes the algorithm of this_image, which seemingly only
worked by chance for the test case; hopefully it now works alway
Hi
This is the third part of the fixing for
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47855
This patch contains the length computation/refinement for insn patterns
"*thumb2_movsi_insn", "*thumb2_cbz" and "*thumb2_cbnz".
At the same time this patch revealed two bugs. The first is the maximum o
101 - 126 of 126 matches
Mail list logo
