Hi all,
Since patch [1] has been applied, that is in GCC 4.7, it's not possible
to build a tri-arch GCC (o32, n32, 64), using mips-linux-gnu as the host
triplet (that is defaulting to o32). In that case mips/t-tpbit is not
included anymore, and while the build succeeds, the resulting
libgcc_s.so
Aurelien Jarno writes:
> 2012-04-28 Aurelien Jarno
>
> * config.host (mips64*-*-linux*, mipsisa64*-*-linux*): Remove.
> (mips*-*-linux*): Include mips/t-tpbit when long double is
> 16 bytes long.
Thanks, applied to trunk and 4.7 branch.
Richard
Hi guys,
Please, take a look at this patch. It fixes the invalid star symbol
processing in validate_switches function reported in GCC bugzilla:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51020
With this patch invalid options are no longer accepted by the
compiler (see new testcase for more deta
Hi,
On 04/28/2012 05:24 AM, Jason Merrill wrote:
On 04/27/2012 09:42 PM, Paolo Carlini wrote:
In particular about the exact meaning of the FIXME? More generally, is
the issue here matter of compile-time optimization? Like we want to save
work when we actually *know* the type even in template co
Looks like people who want to play with optimization options are still tripped
by the fact that optimizations are not enabled unless -O is given (even though
it's documented in the manual now). Can we add a warning for that like below?
Untested beside bubblestrap. I suppose this will produce no
On 04/27/2012 06:25 PM, Ulrich Weigand wrote:
Bernd Schmidt wrote:
We're creating new pseudos, and while we're resizing some data
structures, we aren't doing it for everything.
@@ -3983,7 +3983,8 @@ find_moveable_pseudos (void)
last_moveable_pseudo = max_reg_num ();
- fix_reg_equiv_in
Hi,
arg_pointer and frame_pointer are handled as special cases in
based_loc_descr.
(plus:DI (reg/f:DI 16 argp)
(const_int -20 [0xffec]))
is perfectly valid when Pmode == DImode and DWARF2_ADDR_SIZE is 32bit
with ptr_mode == SImode. This patch fixes ICE on the 2 testcases here.
O
On Tue, Apr 17, 2012 at 3:11 PM, Steven Bosscher wrote:
> On Wed, Apr 18, 2012 at 12:04 AM, Steven Bosscher
> wrote:
>> Hello,
>>
>> This is another step towards moving GIMPLE_SWITCH expansion to an
>> earlier point in the pipeline.
>>
>> With the attached patch, some of the logic from stmt.c:ad
This patch allows us to recognize that even if the argument to memcpy
lives across the call, we can allocate it to a call-used register by
reusing the return value of the function.
First, the patch sets the existing "fn spec" attribute for
memcpy/memmove. This is translated to a new form of
C
Il 27/04/2012 18:43, H.J. Lu ha scritto:
> On Fri, Apr 27, 2012 at 3:01 AM, Paolo Bonzini wrote:
>> This patch teaches phiopt to look at phis whose arguments are -1 and 0,
>> and produce negated setcc statements.
>>
>> Bootstrapped/regtested x86_64-pc-linux-gnu, together with the patch
>> for pr53
> Le 06/04/2012 17:27, Pascal Obry a écrit :
> >
> > Back on this! It turn out that this breaks the shared Ada runtime.
> > Indeed, exported variables on Ada packages in a DLLs are only accessible
> > when linking against DLL (thanks to runtime pseudo reloc).
> >
> > With the patch applied it is
On Thu, Oct 6, 2011 at 1:36 AM, Richard Guenther wrote:
>
> This handles the case of CSEing part of an SSA name that is stored
> to memory and defined with a composition like COMPLEX_EXPR or
> CONSTRUCTOR. This fixes the remaining pieces of PR38884 and
> PR38885.
>
> Bootstrapped and tested on x8
Hello all,
I did a backport of the powerpc64-freebsd support to the 4.7 branch,
here the results:
http://gcc.gnu.org/ml/gcc-testresults/2012-04/msg02768.html
http://gcc.gnu.org/ml/gcc-testresults/2012-04/msg02767.html
Is the attached/below ok to commit to 4.7 branch?
TIA,
Andreas
libstdc++:
Hello,
the attached follows the precisions on the definition of is_modulo in
DR 612. I believe this is what the values always should have been, so I
didn't make the change conditional to C++11.
PR 22200 can remain open if people want to discuss the interaction with
-fwrapv, but false is the
On Sat, Apr 28, 2012 at 5:41 PM, Marc Glisse wrote:
> Hello,
>
> the attached follows the precisions on the definition of is_modulo in DR
> 612. I believe this is what the values always should have been, so I didn't
> make the change conditional to C++11.
Thanks for the patch.
I think 'char' sho
On Fri, Apr 27, 2012 at 4:46 PM, Dodji Seketeli wrote:
> Dodji Seketeli writes:
>
>
>> Tested on x86_64-unknown-linux-gnu against trunk. Bootstrap for all
>> languages is still underway.
>>
>> gcc/c-family/
>>
>> * c.opt (Wvarargs): Define new option.
>>
>> gcc/
>> builtins.c (fold_
On Fri, Apr 27, 2012 at 4:45 PM, Dodji Seketeli wrote:
> Dodji Seketeli writes:
>
>
>> Tested on x86_64-unknown-linux-gnu against trunk. Bootstrap is still
>> running ...
>>
>> * builtins.c (fold_builtin_next_arg): Unwinds to the first
>> location in real source code.
>> ---
>> gcc/
On Sat, 28 Apr 2012, Gabriel Dos Reis wrote:
On Sat, Apr 28, 2012 at 5:41 PM, Marc Glisse wrote:
Hello,
the attached follows the precisions on the definition of is_modulo in DR
612. I believe this is what the values always should have been, so I didn't
make the change conditional to C++11.
On 04/28/2012 07:12 AM, Paolo Carlini wrote:
isn't, but clearly can be instantiation dependent. Then, I guess the way
I'm proposing to handle this is by starting some sort of embryonic
instantiation_dependent_expression_p and using it only here, for now,
like the attached (which passes on x86_64-
On 04/25/2012 05:07 AM, Dodji Seketeli wrote:
+ /* If the first token we got was a padding token, let's put
+it back into the stream so that cpp_get_token will get it
+first; and if we are currently expanding a macro, don't
+forget that information. */
On 04/25/2012 11:31 AM, Dodji Seketeli wrote:
+#define EXPANSION_POINT_LOCATION_FILE(LOC) \
+ ((expand_location_to_expansion_point (LOC)).file)
+#define EXPANSION_POINT_LOCATION_LINE(LOC) \
+ ((expand_location_to_expansion_point (LOC)).line)
+#define EXPANSION_POINT_LOCA
21 matches
Mail list logo
