On Thu, Nov 21, 2013 at 12:19 AM, Zdenek Dvorak
wrote:
> Hi,
>
>> This patch works on the intrinsic calls handling issue in IVOPT mentioned
>> here:
>> http://gcc.gnu.org/ml/gcc-patches/2010-10/msg01295.html
>>
>> In find_interesting_uses_stmt, it changes
>>
>> arg = expr
>> __builtin_xxx (arg)
>
Hi all,
I have just committed a completely obvious one-line patch for an
ICE-on-invalid problem:
http://gcc.gnu.org/viewcvs/gcc?view=revision&revision=205304
Cheers,
Janus
On Fri, 22 Nov 2013, Cong Hou wrote:
IMHO, if PR56788 was fixed, you wouldn't have this issue, and if PR56788
doesn't get fixed, I'll post a patch to remove _mm_frcz_sd and the
associated builtin, which would solve your issue as well.
I agree. Then I will wait until your patch is merged to the
Hi,
This is a one line patch to an unexpected behaviour noticed from ARM
and x86 when testing the D frontend.
---
import core.stdc.stdio;
import core.stdc.stdint;
void test(void* p)
{
uint64_t pl = cast(uint64_t)p;
uint64_t p2 = cast(uint64_t)cast(int)p;
int tmp = cast(int)p;
uin
Tested on x86_64-suse-linux, applied on the mainline as obvious.
2013-11-23 Eric Botcazou
* gimplify.h (recalculate_side_effects): Delete.
* gimplify.c (recalculate_side_effects): Make static and add comment.
ada/
* gcc-interface/trans.c (Loop_Statement_to_gnu): Set TR
Iain Buclaw writes:
> Currently, GCC is converting the expression to a signed integer
> instead of an unsigned one. Does a test for the testsuite need to be
> written for this?
The C standard makes this implementation-defined, and GCC defines it
like this (*Note (gcc) Arrays and pointers implem
On 23 November 2013 10:46, Andreas Schwab wrote:
> Iain Buclaw writes:
>
>> Currently, GCC is converting the expression to a signed integer
>> instead of an unsigned one. Does a test for the testsuite need to be
>> written for this?
>
> The C standard makes this implementation-defined, and GCC d
Hello!
Attached patch fixes PR56788, where _mm_frcz_{ss,sd} intrinsics
ignored their second argument.
As explained in the PR [1], gcc implements two-operand "vector-merge"
form as documented in Microsoft's definition [2]. However, in contrast
to other SSE scalar insns, the instruction itself clea
Jakub Jelinek wrote:
>Hi!
>
>This PR is about what I understood (can't reproduce, seems ltoish)
>about reassoc now creating say _24 = (int) 0; with _Bool 0, and
>forwprop ICEing on that.
>
>The patch fixes forwprop not to ICE on it (I think we don't require
>the IL to be always folded), and reasso
While looking at the index for -fsanitize=, I found out that it – and
many other options – lack the @opindex. Attached is an attempted to add
the missing ones.
OK?
Tobias
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 0708836..b41c44c 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/do
This appears to be adding a new libgcc target macro; please document it in
tm.texi.in and regenerate tm.texi.
--
Joseph S. Myers
jos...@codesourcery.com
Kugan writes:
> This RFC patch series implements a simple align divisor shift dividend
> method.
>
> Regression tested on arm-none-linux-gnueabi with no issues.
>
> OK?
>
> Thanks,
> Kugan
>
> +2013-11-22 Kugan Vivekanandarajah
> +
> + * libgcc/libgcc2.c (__udivmoddi4): Define new implemen
While working with Uli on the PPC64 LE ELFv2 implementation, we
discovered that one of the changes to argument passing introduced new
regressions in the struct-layout part of the testsuite, which should
not have changed.
Uli tracked this down to a change in the mode for multi-register
parameters t
Hi Uros!
Thanks for lookin at this. I am a real newcomer to 387, and it took me a long
time perusing the Intel doc, as well as glibc sources, to come up with that.
The “reference” implementation of these FPU functions, the one I am confident
in, is that in config/fpu-glibc.h: i.e., the function
On Sat, Nov 23, 2013 at 4:38 AM, Iain Buclaw wrote:
>
> OK, I've checked that document, and there's also a comment with it.
> Apparently someone spotted this before.
>
> @c ??? We've always claimed that pointers were unsigned entities.
> @c Shouldn't we therefore be doing zero-extension? If so, t
The earlier patch fixed the testcase, but it seemed to me that
build_aggr_init still ought to do the right thing here.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit cfde6c1e56ecbbd098de20451cc718cedeb8dffd
Author: Jason Merrill
Date: Wed Nov 6 09:33:24 2013 -0500
PR c++/58868
On 10/07/2013 09:38 AM, Alexander Ivchenko wrote:
__cxa_throw_bad_array_new_length and __cxa_throw_bad_array_new_length
are generated with -fno-exceptions right now. The attached patch fixes
that problem. Bootstrapped and regtested on x86_64-unknown-linux-gnu:
Thanks. The underlying code has c
The 'worker' field has pointer type
tree worker_type = lang_hooks.types.make_type (RECORD_TYPE);
tree worker_ptr = build_pointer_type (worker_type);
[...]
tree worker = add_field ("worker", worker_ptr, parent);
so it needs to be dereferenced before being subject to COMPONENT_REF.
Tested on
On Sat, Nov 23, 2013 at 4:30 PM, FX wrote:
> Thanks for lookin at this. I am a real newcomer to 387, and it took me a long
> time perusing the Intel doc, as well as glibc sources, to come up with that.
> The “reference” implementation of these FPU functions, the one I am confident
> in, is tha
On Sat, Nov 23, 2013 at 5:48 PM, Uros Bizjak wrote:
>> Thanks for lookin at this. I am a real newcomer to 387, and it took me a
>> long time perusing the Intel doc, as well as glibc sources, to come up with
>> that. The “reference” implementation of these FPU functions, the one I am
>> confide
On Sat, Nov 23, 2013 at 6:24 PM, Uros Bizjak wrote:
> On Sat, Nov 23, 2013 at 5:48 PM, Uros Bizjak wrote:
>
>>> Thanks for lookin at this. I am a real newcomer to 387, and it took me a
>>> long time perusing the Intel doc, as well as glibc sources, to come up with
>>> that. The “reference” impl
bootstrap and regression of the updated patch pass.
On Sat, Nov 23, 2013 at 12:05 AM, Wei Mi wrote:
> On Thu, Nov 21, 2013 at 12:19 AM, Zdenek Dvorak
> wrote:
>> Hi,
>>
>>> This patch works on the intrinsic calls handling issue in IVOPT mentioned
>>> here:
>>> http://gcc.gnu.org/ml/gcc-patches/
Ulrich Weigand pointed out that the Go frontend is generating invalid
GIMPLE for a call to an interface method: the function type does not
match the number of arguments passed. I'm surprised this works at all,
but in any case this patch fixes it.
Fixing this problem showed that the frontend was n
OK.
Jason
OK.
Jason
On 11/10/2013 05:26 AM, Paolo Carlini wrote:
this is the issue with -Waddress caused by the fix for c++/56930. I'm
handling it as already described, that is by adding a bool parameter to
c_common_truthvalue_conversion.
Why not handle this by making that warning respect
c_inhibit_evaluation_war
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the aarch64 port.
Ok?
* config/aarch64/aarch64.c
(aapcs_vfp_sub_candidate): Use wide-int
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the alias analysis code.
Ok?
* alias.c
(ao_ref_from_mem): Use wide-int interfaces.
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the ada front-end.
Ok?
ada:
* gcc-interface/cuintp.c
(UI_From_gnu): Use wide-int interfa
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the arc port.
Ok?
* config/arc/arc.c
(arc_can_use_doloop_p): Use wide-int interfaces.
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the builtins code.
Ok?
* builtins.c
(get_object_alignment_2): Use wide-int interfaces.
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the bfin port.
Ok?
* config/bfin/bfin.c
(bfin_local_alignment): Use wide-int interfaces.
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the c front end.
Ok?
c:
* c-decl.c
(check_bitfield_type_and_width): Use TYPE_SIGN.
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the build system (make).
Ok?
* Makefile.in
(RTL_H, CFGLOOP_H, C_COMMON_H, TREE_FLOW_H):
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the avr port.
Ok?
* config/avr/avr.c
(avr_out_round): Use wide-int interfaces.
(
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the arm port.
Ok?
* config/arm/arm.c
(aapcs_vfp_sub_candidate): Use wide-int interfaces.
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the go front end.
Ok?
* godump.c: Include wide-int-print.h.
(go_output_typedef): Use wid
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the avr port.
Ok?
* config/avr/avr.c
(avr_out_round): Use wide-int interfaces.
(
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the graphite code.
Ok?
* graphite-clast-to-gimple.c
(gmp_cst_to_tree): Use wide-int inte
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the C++ front end.
Ok?
cp:
* call.c: Include wide-int.h.
(type_passed_as): Use INT_CST_L
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the gen*.c code, excluding gengtype.
Ok?
* genemit.c
(gen_exp): Add CONST_WIDE_INT case.
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the decimal floating point code.
Ok?
* dfp.c: Include wide-int.h.
(decimal_real_to_integ
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the documentation.
Ok?
* doc/generic.texi
(Constant expressions): Use wide-int interface
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the gengtype code.
Ok?
* gengtype.c: Remove include of double-int.h.
(do_typedef): Use w
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the fortran front end.
Ok?
fortran:
* target-memory.c: Include wide-int.h.
(gfc_interpre
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the msp430 port.
Ok?
* config/msp430/msp430.c
(msp430_attr): Use wide-int interfaces.
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the nds32 port.
Ok?
* config/nds32/nds32.c
(nds32_insert_attributes): Use wide-int inter
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the cfg code.
Ok?
* cfgloop.c
(alloc_loop): Initialize nb_iterations_upper_bound and
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the OpenMP code.
Ok?
* omp-low.c
(scan_omp_1_op): Use wide-int interfaces.
diff --git
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the darwin port.
Ok?
* config/darwin.c
(darwin_mergeable_constant_section): Use wide-int
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the hook code.
Ok?
* hooks.h: Include wide-int.h rather than double-int.h.
(hook_bool_di
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the dwarf code.
Ok?
* dwarf2out.c
(get_full_len): New.
(dw_val_equal_p): Add cas
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the scheduler code.
Ok?
* sched-vis.c
(print_value): Handle CONST_WIDE_INT.
* se
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the first half of the rtl code.
Ok?
wide-int-rtl.diffs.txt.bz2
Description: BZip2 compressed data
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the ipa code.
Ok?
* ipa-devirt.c
(get_polymorphic_call_info): Use wide-int interfaces.
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the half of the rtl code.
Ok?
* dojump.c
(prefer_and_bit_test): Use wide-int interfaces.
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the loop code.
Ok?
* loop-doloop.c
(doloop_modify): Use wide-int interfaces.
(do
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the test suite.
Ok?
testsuite:
* gcc.dg/tree-ssa/pr45427.c: Update to look for 0x0 instead of 0.
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the tree-vec code.
Ok?
* tree-vect-data-refs.c
(vect_prune_runtime_alias_test_list): Use
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the lto code.
Ok?
* lto-streamer-in.c
(input_cfg): Use wide-int interfaces.
(lto
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the rs6000 port.
Ok?
* config/rs6000/predicates.md
(any_operand): Add const_wide_int.
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the new wide-int code.
Ok?
wide-int-wide.diffs.txt.bz2
Description: BZip2 compressed data
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the gimple code.
Ok?
* gimple.c
(preprocess_case_label_vec_for_gimple): Use wide-int int
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the reload code.
Ok?
* postreload.c
(reload_cse_simplify_set): Use wide-int interfaces.
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the i386 port.
Ok?
* config/i386/i386.c: Include wide-int.h.
(ix86_data_alignment): Use
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the java front end.
Ok?
java:
* boehm.c: Include wide-int.h.
(mark_reference_fields): Us
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the Objective-C front end.
Ok?
objc:
* objc-act.c: Include wide-int.h.
(objc_decl_method
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the random pieces that didn't seem to fit
nicely into other bins.
Ok?
* coretypes.h
(st
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the real.c code.
Ok?
* real.c: Include wide-int.h.
(real_to_integer2): Delete.
(
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the sparc port.
Ok?
* config/sol2-c.c
(solaris_pragma_align): Use tree_fits_uhwi_p.
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the tree code.
Ok?
wide-int-tree.diffs.txt.bz2
Description: BZip2 compressed data
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the tree-saa code.
Ok?
wide-int-tree-ssa.diffs.txt.bz2
Description: BZip2 compressed data
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the vax port.
Ok?
* config/vax/vax.c: Include wide-int.h.
(vax_float_literal): Use real_
On 11/06/2013 05:56 AM, Paolo Carlini wrote:
in this bug, filed by Zack, we loop forever after error in
constant_value_1. Straightforward thing to do, detect and break out.
This doesn't handle mutual infinite recursion, such as the modified
testcase below. I think the right answer is to make
On Nov 23, 2013, at 11:22 AM, Mike Stump wrote:
> Richi has asked the we break the wide-int patch so that the individual port
> and front end maintainers can review their parts without have to go through
> the entire patch.This patch covers the test suite.
>
> Ok?
Ok.
On Nov 23, 2013, at 11:22 AM, Mike Stump wrote:
> Richi has asked the we break the wide-int patch so that the individual port
> and front end maintainers can review their parts without have to go through
> the entire patch.This patch covers the Objective-C front end.
>
> Ok?
Ok.
On Nov 23, 2013, at 11:21 AM, Mike Stump wrote:
> Richi has asked the we break the wide-int patch so that the individual port
> and front end maintainers can review their parts without have to go through
> the entire patch.This patch covers the darwin port.
>
> Ok?
Ok.
On Nov 23, 2013, at 11:21 AM, Mike Stump wrote:
> Richi has asked the we break the wide-int patch so that the individual port
> and front end maintainers can review their parts without have to go through
> the entire patch.This patch covers the darwin port.
>
> Ok?
Ok.
On Sat, Nov 23, 2013 at 11:21:21AM -0800, Mike Stump wrote:
> Richi has asked the we break the wide-int patch so that the individual port
> and front end maintainers can review their parts without have to go through
> the entire patch.This patch covers the fortran front end.
>
> Ok?
>
> +
On 11/07/2013 02:14 PM, Easwaran Raman wrote:
Before r193504, if a method can not be overridden, LOOKUP_NONVIRTUAL
is set and the call is direct. The changes at r193504 (to fix PR
c++/11750) caused a regression to this behavior. This patch attempts
to fix that. Bootstraps and no test regressions
I believe that our current practice is to have one error and then use
inform for follow-on messages. OK with that change.
Jason
On 10/21/2013 02:05 PM, Paolo Carlini wrote:
Thus the idea
of resolving the inconsistency by removing completely one of the two
checks: that in grokfndecl is more precise (separate messages for
cv-qualifiers and ref-qualifiers) and seems the best candidate. The
patch below passes testing modulo t
On Sat, Nov 23, 2013 at 12:16 PM, Steve Kargl
wrote:
> On Sat, Nov 23, 2013 at 11:21:21AM -0800, Mike Stump wrote:
>> Richi has asked the we break the wide-int patch so that the individual port
>> and front end maintainers can review their parts without have to go through
>> the entire patch.
On Sat, Nov 23, 2013 at 1:31 PM, Andrew Pinski wrote:
> On Sat, Nov 23, 2013 at 12:16 PM, Steve Kargl
> wrote:
>> On Sat, Nov 23, 2013 at 11:21:21AM -0800, Mike Stump wrote:
>>> Richi has asked the we break the wide-int patch so that the individual port
>>> and front end maintainers can review t
On Sat, Nov 23, 2013 at 11:19 AM, Mike Stump wrote:
> Richi has asked the we break the wide-int patch so that the individual port
> and front end maintainers can review their parts without have to go through
> the entire patch.This patch covers the aarch64 port.
+ wide_int w = real_to_int
Hi!
Now that it's nicely working, I'd like to publically announce the
Build Robot. As suggested, here's a patch adding it to GCC's
homepage's "Development" section as well as to the "News":
Index: index.html
===
RCS file: /cvs/gcc/w
On 10/20/2013 12:07 PM, Paolo Carlini wrote:
case COMPONENT_REF:
+ if (is_overloaded_fn (TREE_OPERAND (t, 1)))
+ return t;
Hmm, I'd be inclined to strip the COMPONENT_REF in this case to produce
something that's actually usable as a constant. Does that work?
Jason
OK.
Jason
On 10/12/2013 09:34 PM, Paolo Carlini wrote:
this ICE on invalid, a 4.8/4.9 Regression, simply started when
build_lang_decl_loc was introduced, which wants a location as first
argument: when the declarator is null, we can't pass the location as
declarator->id_loc. For now input_location can do, I
OK.
On Sat, Nov 23, 2013 at 11:21:10AM -0800, Mike Stump wrote:
> * dfp.c: Include wide-int.h.
> (decimal_real_to_integer2): Use wide-int interfaces and rename to
> decimal_real_to_integer.
> * dfp.h
> (decimal_real_to_integer2): Return a wide_int and rename to
> de
On Sat, Nov 23, 2013 at 01:31:04PM -0800, Andrew Pinski wrote:
> On Sat, Nov 23, 2013 at 12:16 PM, Steve Kargl
> wrote:
> > On Sat, Nov 23, 2013 at 11:21:21AM -0800, Mike Stump wrote:
> >> Richi has asked the we break the wide-int patch so that the individual
> >> port and front end maintainers c
On Mon, Nov 4, 2013 at 1:51 PM, Wei Mi wrote:
> Thanks! The three patches are commited as r204367, r204369 and r204371.
>
r204369 caused:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59020
--
H.J.
On Sat, Nov 23, 2013 at 4:26 PM, Steve Kargl
wrote:
> On Sat, Nov 23, 2013 at 01:31:04PM -0800, Andrew Pinski wrote:
>> On Sat, Nov 23, 2013 at 12:16 PM, Steve Kargl
>> wrote:
>> > On Sat, Nov 23, 2013 at 11:21:21AM -0800, Mike Stump wrote:
>> >> Richi has asked the we break the wide-int patch so
On 23 November 2013 19:19, Mike Stump wrote:
> Richi has asked the we break the wide-int patch so that the individual port
> and front end maintainers can review their parts without have to go through
> the entire patch.This patch covers the arc port.
>
> Ok?
>
wide-int.h says widest_int is
On 11/23/2013 02:21 PM, Mike Stump wrote:
- if (SCALAR_FLOAT_MODE_P (mode))
+#if TARGET_SUPPORTS_WIDE_INT == 0
+ if (!SCALAR_FLOAT_MODE_P (mode))
+ {
+ mem_loc_result->dw_loc_oprnd2.val_class
+ = dw_val_class_const_double;
+ mem_loc_
Steve Kargl writes:
> On Sat, Nov 23, 2013 at 01:31:04PM -0800, Andrew Pinski wrote:
>> On Sat, Nov 23, 2013 at 12:16 PM, Steve Kargl
>> wrote:
>> > On Sat, Nov 23, 2013 at 11:21:21AM -0800, Mike Stump wrote:
>> >> Richi has asked the we break the wide-int patch so that the individual
>> >> por
On 11/23/2013 02:20 PM, Mike Stump wrote:
@@ -2605,8 +2606,7 @@ cp_tree_equal (tree t1, tree t2)
switch (code1)
{
case INTEGER_CST:
- return TREE_INT_CST_LOW (t1) == TREE_INT_CST_LOW (t2)
- && TREE_INT_CST_HIGH (t1) == TREE_INT_CST_HIGH (t2);
+ return wi::to_widest
Reportedly in the new PPC ELF v2 ABI calls to varargs functions act
differently from calls to normal functions. The Go compiler can call C
functions directly using //extern comments, but it can't represent a C
varargs function. Rather than extend the compiler, this patch changes
the library so th
On 11/23/2013 08:47 PM, Jason Merrill wrote:
On 11/23/2013 02:21 PM, Mike Stump wrote:
- if (SCALAR_FLOAT_MODE_P (mode))
+#if TARGET_SUPPORTS_WIDE_INT == 0
+ if (!SCALAR_FLOAT_MODE_P (mode))
+{
+ mem_loc_result->dw_loc_oprnd2.val_class
+= dw_val_class_const_do
1 - 100 of 104 matches
Mail list logo
