Hi,
I committed the patch below as obvious.
Index: intrinsics/time_1.h
===
--- intrinsics/time_1.h (revision 187921)
+++ intrinsics/time_1.h (working copy)
@@ -158,10 +158,11 @@ gf_cputime (long *user_sec, long *user_u
struct tms
Marcus Shawcroft writes:
> This patch adds an implementation of integer iterators.
Nice. A few comments from an onlooker (on top of what Stephen said).
> +/* Since GCC does not construct a table of valid constants,
> + we have to accept any int as valid. No cross-checking can
> + be done.
Gabriel Dos Reis writes:
> if this coding standard is going to be adopted as a GNU coding
> convention, then you have to be flexible and allow yourself to see
> beyond the past written in C. You have to ask yourself: how do I
> want the codebase to look like in 10, 15, 20, 25 years.
Er, sure, bu
On Sun, May 27, 2012 at 4:55 AM, Miles Bader wrote:
> Gabriel Dos Reis writes:
>> if this coding standard is going to be adopted as a GNU coding
>> convention, then you have to be flexible and allow yourself to see
>> beyond the past written in C. You have to ask yourself: how do I
>> want the c
On 05/24/12 09:03, Richard Guenther wrote:
If you don't hear from somebody else in 24h the patch is ok as-is
(can you do some grepping whether there are callers of build_constructor
that set TREE_SIDE_EFFECTS on it afterwards?)
I committed the patch. grepping C & C++ sources didn't show calle
On Fri, May 25, 2012 at 8:34 PM, Diego Novillo wrote:
> Fix parser initialization and parsing of gimple_assign.
>
> This patch fixes the parser to use the new line map table
> initialization code. It was not setting the allocation function
> pointers properly.
>
> Additionally, we were only expect
Sriraman Tallam writes:
> Any reason why gcc should not be made to prefer libgcc_s.so too like g++?
It's controlled by the -shared-libgcc and -static-libgcc options.
The -shared-libgcc option is the default for g++ because several years
ago a shared libgcc was required to make exception handlin
Hi,
This patch implements static branch prediction for loop exit
conditions that cannot be identified by original heuristic (edge->dst
is outside of the loop). It can find extra loop exits for short
circuit conditions.
Bootstrapped and passed gcc testsuite.
Is it ok for trunk?
Thanks,
Dehao
gc
