> -Original Message-
> From: Richard Henderson [mailto:r...@redhat.com]
> Sent: Tuesday, November 25, 2014 5:25 PM
> To: Zhenqiang Chen
> Cc: Marcus Shawcroft; gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH, AARCH64] Fix ICE in CCMP (PR64015)
>
> On 11/25/2014 09:41 AM, Zhenqiang Chen wro
This patch cleans up Fortran's option handling and moves it closer to
the common way of option handling. That's a nice cleanup and
additionally, as Manuel points out in the PR, there are a couple of
reasons why this makes sense in addition. I have not yet touched all
options but one has to star
> -Original Message-
> From: Jeff Law [mailto:l...@redhat.com]
> Sent: Wednesday, December 10, 2014 3:16 AM
> To: Segher Boessenkool; Zhenqiang Chen
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] Fix PR 61225
>
> On 12/09/14 12:07, Segher Boessenkool wrote:
> > On Tue, Dec 09, 2014
> -Original Message-
> From: Richard Henderson [mailto:r...@redhat.com]
> Sent: Wednesday, December 10, 2014 8:55 AM
> To: Zhenqiang Chen
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: [Ping] [PATCH, ifcvt] Fix PR63917
>
> On 12/04/2014 05:16 PM, Zhenqiang Chen wrote:
> > +static rtx
> > +
A bit I forgot in the earlier C++14 constexpr work.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit 0b9dbcebc4d3bf5e9281889f34d189fb7c42dde3
Author: Jason Merrill
Date: Thu Dec 11 22:19:36 2014 -0500
* c-cppbuiltin.c (c_cpp_builtins): Enable C++14 __cpp_constexpr.
diff --git a/gcc
The C++ VLA paper, N3639, was voted into and then back out of the C++14
standard, and currently seems likely not to ever be part of a published
standard. So I'm backing out most of my changes for that paper, such
that -std=c++14 has the same VLA support as other standard modes. We no
longer t
2014-12-10 21:37 GMT+08:00 Richard Biener :
> On Wed, Dec 10, 2014 at 6:16 AM, Chung-Ju Wu wrote:
>>
>> Thanks for the suggestion.
>> The followings are proposed patch to adjust comment:
>>
>> Index: contrib/ChangeLog
>> ===
>> --- co
It seems that my strict reading of the standard conflicts with existing
practice in a way that is not useful. So I'm reverting my earlier patch.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit 9dfef51ff302e644acf0111685a7451867049959
Author: Jason Merrill
Date: Wed Dec 10 17:33:19 2014
We want to deal with initialization of an array reference/init-list
temporary the same way that we handle initialization of an array variable.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit ad88fa39b2c68d806b58563dfe1e19ecf8d143ba
Author: Jason Merrill
Date: Wed Dec 10 14:14:05 2014 -0
On Fri, 12 Dec 2014, Joseph Myers wrote:
> At least one target for this port should be added to
> contrib/config-list.mk (and you should verify that the port builds cleanly
> with --enable-werror-always, for both 32-bit and 64-bit hosts, when
> building using current trunk GCC).
While doing that,
Ping? Already applied to arm/embedded-4_9-branch, is it OK for trunk?
-Hale
> -Original Message-
> From: Joey Ye [mailto:joey.ye...@gmail.com]
> Sent: Thursday, November 27, 2014 10:01 AM
> To: Hale Wang
> Cc: gcc-patches
> Subject: Re: [PATCH, ARM, libgcc] New aeabi_idiv function for arm
Use of `%s' in diagnostics is long obsoleted by %qs (in this case, using
%qE with the identifier directly, rather than using IDENTIFIER_POINTER, is
preferred).
INTVAL / UINTVAL return HOST_WIDE_INT / unsigned HOST_WIDE_INT, not long /
unsigned long. You have lots of uses of fprintf that presum
Do you have a reason for using fp-bit instead of soft-fp?
libgcc files are generally GPL+exception, not LGPL without exception with
a very old FSF address (config/visium/div64.c, mod64.c,
set_trampoline_parity.c, udiv64.c, udivmod64.c, umod64.c)
--
Joseph S. Myers
jos...@codesourcery.com
gcc/testsuite/ChangeLog:
2014-12-11 Eric Botcazou
* lib/target-supports.exp (check_profiling_available): Return 0 for
Visium.
(check_effective_target_tls_runtime): Likewise.
(check_effective_target_logical_op_short_circuit): Return 1 for Visium.
* gcc.dg
gcc/ChangeLog
2014-12-11 Eric Botcazou
* config.gcc: Add Visium support.
* configure.ac: Likewise.
* configure: Regenerate.
* doc/invoke.texi: Document Visium options.
* doc/md.texi: Document Visium constraints.
* common/config/visium: New direct
libgcc/ChangeLog
2014-12-11 Eric Botcazou
* config.host: Add Visium support.
* config/visium: New directory.
--
Eric BotcazouIndex: config.host
===
--- config.host (revision 218617)
+++ config.host (work
ChangeLog
2014-12-11 Eric Botcazou
* config.sub: Update from upstream config repo.
* configure.ac: Add Visium support.
* configure: Regenerate.
--
Eric BotcazouIndex: config.sub
===
--- config.sub (revis
mmary ===
# of expected passes162014
# of unexpected failures12
# of expected failures 188
# of unsupported tests 3592
/home/eric/build/gcc/visium-elf/gcc/xgcc version 5.0.0 20141211
(experimental) [trunk revision 218617] (GCC)
after they are applied (on a x86_64-
On Dec 11, 2014, at 1:32 AM, Kyrill Tkachov wrote:
> the patch that adds the libstdc++.exp changes at
> https://gcc.gnu.org/ml/gcc-patches/2014-12/msg00952.html using the new
> target-utils.exp file is ok too then?
Ok.
The doc reads:
`(pc)'
This refers to the address of the _current_ insn. It might have
been more consistent with other usage to make this the address of
the _next_ insn but this would be confusing because the length of
the current insn is to be computed.
That's incorrect for f
The char's in gcc.dg/builtin-arith-overflow-1.c are almost all explicitly
signed or unsigned, except for 2 of them, but that's enough to make it fail
for targets whose char is unsigned.
Tested on x86-64 and a private port, applied on mainline as obvious.
2014-12-11 Eric Botcazou
*
Hi,
IPA comdats performs a dataflow identifying section where every symbol is used.
It sanity checks that everything is reachable. This sanity check shows latent
issue with unreachable function removal.
symbol_table::remove_unreachable_nodes has parameter before_inlining_p that
says whether extern
> Note that I think the place of the check is unfortunate as you for example
> will not remove the argument if it is unused. In fact I'm not yet sure
> what transform exactly we are disabling. I am guessing we are
> passing an aggregate by value that resides at a bit-aligned offset
> of some oute
Hi,
On Thu, Dec 11, 2014 at 07:16:43PM +0100, Jan Hubicka wrote:
> > On Thu, Dec 11, 2014 at 06:06:55PM +0100, Jan Hubicka wrote:
> > > Hi,
> > > in firefox .optimized dumps one can see few places where
> > > __builtin_unreachable
> > > is called (as a result of devirtualization code proving the
Hi all,
Please backport the following to gcc 4.9
https://gcc.gnu.org/ml/gcc-patches/2014-10/msg02980.html.
There has been a request to get the fixes that went into gcc trunk for
gccgo ppc64 & ppc64le backported into gcc 4.9.
2014-12-11 Lynn Boger
* libgo/mksysinfo.sh: Add ioctl const
Hello,
after HONOR_NANS, I am turning the other HONOR_* macros into functions. As
a reminder, the goal is both to make uses shorter and to fix the answer
for non-native vector types.
Bootstrap+testsuite on x86_64-linux-gnu.
2014-12-12 Marc Glisse
* real.h (HONOR_SNANS, HONOR_INFI
On 12/11/2014 02:19 PM, Jason Merrill wrote:
On 12/11/2014 12:44 PM, Aldy Hernandez wrote:
This context then gets changed here:
/* For local statics lookup proper context die. */
if (TREE_STATIC (decl)
&& DECL_CONTEXT (decl)
&& TREE_CODE (DECL_CONTEXT (decl)) == FUN
On 12/11/2014 04:25 AM, Dominik Vogt wrote:
> Update: If I disable the custom s390x code and switch to the
> implementation just using libffi for reflection calls, the same
> crash occurs with the testing/quick libgo test case. The called
> function sees a bogus value written by the synamic linke
On 12/11/2014 01:06 AM, Dominik Vogt wrote:
> reflect.call
> ../../../libgo/runtime/go-reflect-call.c:216
> reflect.call.N13_reflect.Value
>
> GCCDIR/build-go-closure/x86_64-unknown-linux-gnu/libgo/gotest30365/test/value.go:579
> reflect.Call.N13_reflect.Value
>
> GCCDIR/build-g
Looks like `depth' is passed around and never used.
OK for mainline?
commit d1603304423bcb25c69d0f4bf51b142e07274275
Author: Aldy Hernandez
Date: Thu Dec 11 10:51:04 2014 -0800
* dwarf2out.c (gen_lexical_block_die): Remove unused `depth'
parameter.
(gen_inlined_subrout
On 12/11/14 11:23, Jason Merrill wrote:
On 12/11/2014 02:19 PM, Jason Merrill wrote:
On 12/11/2014 12:44 PM, Aldy Hernandez wrote:
This context then gets changed here:
/* For local statics lookup proper context die. */
if (TREE_STATIC (decl)
&& DECL_CONTEXT (decl)
On 12/11/2014 12:44 PM, Aldy Hernandez wrote:
This context then gets changed here:
/* For local statics lookup proper context die. */
if (TREE_STATIC (decl)
&& DECL_CONTEXT (decl)
&& TREE_CODE (DECL_CONTEXT (decl)) == FUNCTION_DECL)
context_die = lookup_decl_die
OK.
Jason
Sorry - it works exactly as the current optab/expander *in the v2df case*, but
is the same as the previous version of the patch in the other cases.
--Alan
Alan Lawrence wrote:
So I'm afraid I'm not going to get involved in a discussion about
CANNOT_CHANGE_MODE_CLASS on RS6000, and what you mig
here are the non-libstdc++ patches:
--- libgfortran/configure.orig 2014-12-10 22:34:06.0 +0100
+++ libgfortran/configure 2014-12-10 22:33:57.0 +0100
@@ -26447,7 +26447,7 @@
fi
case "$host" in
-*-*-darwin* | *-*-hpux* | *-*-cygwin* | *-*-mingw* )
+*-*-darwin*
Here are the three patches as requested for #64271.
--- libstdc++-v3/config/os/bsd/netbsd/ctype_inline.h.orig 2014-12-10
22:19:05.0 +0100
+++ libstdc++-v3/config/os/bsd/netbsd/ctype_inline.h2014-12-10
22:20:46.0 +0100
@@ -48,7 +48,7 @@
is(const char* __low, const cha
> On Thu, Dec 11, 2014 at 06:06:55PM +0100, Jan Hubicka wrote:
> > Hi,
> > in firefox .optimized dumps one can see few places where
> > __builtin_unreachable
> > is called (as a result of devirtualization code proving the code path to be
> > undefined). There is usually some argument setup for th
> On Dec 11, 2014, at 10:06 AM, Tejas Belagod wrote:
>
>> On 22/11/14 23:41, Andrew Pinski wrote:
>> Hi,
>> After the conditional compare patches, the some of the
>> gcc.target/aarch64/test_frame_*.c testcases start to fail. This was
>> due to no longer duplicating simple_return and causin
On 22/11/14 23:41, Andrew Pinski wrote:
Hi,
After the conditional compare patches, the some of the
gcc.target/aarch64/test_frame_*.c testcases start to fail. This was
due to no longer duplicating simple_return and causing the epilogue to
be duplicated.
This changes the testcases to expect th
On Wed, 2014-12-10 at 23:32 -0500, Ulrich Drepper wrote:
> On Mon, Dec 8, 2014 at 11:36 AM, David Malcolm wrote:
> > Thanks. Overall this is good, a few nitpicks inline below:
>
> I've made the changes and checked in the patch.
...as r218617. Thanks.
The jit subdirectory has its own ChangeLog
I'm seeing this test timeout on glibc 2.13, which I think is because
it doesn't provide __cxa_atexit_thread_impl and so the thread_local
destructor and the notify_all() happen in an unspecified order.
Tested x86_64-linux, committed to trunk.
commit 299704c621dd7afaee7c5fb2a354b40ef41c2eba
Author:
Hi Jason.
After my last set of dwarf changes for locals, I found some target
library building failures which I am now fixing.
The problem at hand is that, by design, the caching code in
gen_variable_die() refuses to use a previously cached DIE if the current
context and the cached context ar
PING - https://gcc.gnu.org/ml/gcc-patches/2014-12/msg00731.html
Tobias Burnus wrote:
> This patch requires that the gfc_error patch has been applied,
> https://gcc.gnu.org/ml/gcc-patches/2014-12/msg00607.html
That patch has now been committed - and my patch still applies, building
and regtesting
On Thu, Dec 11, 2014 at 06:06:55PM +0100, Jan Hubicka wrote:
> Hi,
> in firefox .optimized dumps one can see few places where __builtin_unreachable
> is called (as a result of devirtualization code proving the code path to be
> undefined). There is usually some argument setup for the parameters of
Hi,
in firefox .optimized dumps one can see few places where __builtin_unreachable
is called (as a result of devirtualization code proving the code path to be
undefined). There is usually some argument setup for the parameters of
__builtin_unreachable that are dead. This patch makes it somewhat b
So I'm afraid I'm not going to get involved in a discussion about
CANNOT_CHANGE_MODE_CLASS on RS6000, and what you might want to do there - sorry,
but I don't think I can really contribute anything there. However, I *am* trying
to migrate all platforms off the old reduc_xxx optabs to the new ver
On Thu, Dec 11, 2014 at 11:05:13AM +0100, Richard Biener wrote:
>
> The following patch fixes the performance regression in PR42108
> by allowing PRE and LIM to see the division (to - from) / step
> in translating do loops executed unconditionally. This makes
> them not care for the fact that ste
Hi all
we have merged the gcc-4_9-branch into linaro/gcc-4_9-branch up to
revision 218412 as r218423. We have also backported this set of revisions:
* r213382 as r218352 : [AArch64] arm_neon.h - add vpaddd_f64,
vpaddd_s64, vpaddd_u64 intrinsics
* r214008 as r218354 : [AArch64] Move some code aro
On 11 December 2014 at 10:06, Bin Cheng wrote:
> gcc/testsuite/ChangeLog
> 2014-12-11 Bin Cheng
>
> * gcc.target/aarch64/ldp_stp_2.c: Make test less vulnerable.
> * gcc.target/aarch64/ldp_stp_3.c: Ditto.
OK /Marcus
On 10 December 2014 at 16:34, Renlin Li wrote:
> 2014-12-10 Renlin Li
>
> * config/aarch64/aarch64-cores.def: Change all AARCH64_FL_FPSIMD to
> AARCH64_FL_FOR_ARCH8.
> * config/aarch64/aarch64.c (all_cores): Use FLAGS from aarch64-cores.def
> file
> only.
OK /Marcus
On 10 December 2014 at 13:58, Renlin Li wrote:
> This is a backport patch of
> https://gcc.gnu.org/ml/gcc-patches/2014-12/msg00287.html
>
> aarch64-none-elf has been built and tested on the model, no issue.
> Okay for branch 4.9?
>
> Regards,
> Renlin Li
>
>
> gcc/ChangeLog:
>
> 2014-12-10 Renlin
On 10 December 2014 at 15:30, Kyrill Tkachov wrote:
> 2014-12-10 Kyrylo Tkachov kyrylo.tkac...@arm.com
>
> * config/aarch64/aarch64.c (aarch64_parse_extension): Update error
> message to say +no only when removing extension.
OK /Marcus
Ping.
https://gcc.gnu.org/ml/gcc-patches/2014-12/msg00340.html
Thanks,
Kyrill
On 04/12/14 09:19, Kyrill Tkachov wrote:
On 02/12/14 22:58, Ramana Radhakrishnan wrote:
On Tue, Nov 11, 2014 at 11:55 AM, Kyrill Tkachov wrote:
Hi all,
This is the arm implementation of the macro fusion hook.
It t
On 23 November 2014 at 00:09, Andrew Pinski wrote:
> Hi,
> This is just a rebase of
> https://gcc.gnu.org/ml/gcc-patches/2014-11/msg01615.html as requested
> by https://gcc.gnu.org/ml/gcc-patches/2014-11/msg01736.html. Nothing
> has changed in it.
>
> OK? Built and tested on aarch64-elf with n
On 12/08/2014 11:23 AM, Jan-Benedict Glaw wrote:
On Fri, 2014-11-21 08:45:11 -0500, Andrew MacLeod wrote:
During the flattening of optabs.h, I updated all the config/* files
which were affected. I've been getting spurious failures with
config-list.mk where my changes would "disappear" and tra
OK.
Jason
On Thu, Dec 11, 2014 at 2:49 PM, Martin Liška wrote:
> Hello.
>
> In PR64146, for position independent code IPA ICF should be more careful
> about thunk creation.
> Patch can bootstrap on x86_64-linux-pc and no new regression was seen.
>
> Ready for thunk?
Hmm, does that merge the functions but
k
Hello.
In PR64146, for position independent code IPA ICF should be more careful about
thunk creation.
Patch can bootstrap on x86_64-linux-pc and no new regression was seen.
Ready for thunk?
Thank you,
Martin
>From e57dbf95cf27c2d5da2322ee75dca6361ab59c8a Mon Sep 17 00:00:00 2001
From: mliska
D
On 11 December 2014 at 11:16, David Sherwood wrote:
> Hi Christophe,
>
> Sorry to bother you again. After my clarification email below are you now
> happy for these patches to go in?
>
> Kind Regards,
> David Sherwood.
>
>> -Original Message-
>> From: David Sherwood [mailto:david.sherw...@
David Malcolm writes:
> On Mon, 2014-12-08 at 14:13 +0100, Rainer Orth wrote:
>> Jeff Law writes:
>>
>> > On 12/04/14 15:42, Rainer Orth wrote:
>> >> David Malcolm writes:
>> >>
>> >>> assumed -fgnu89-inline until a recent upstream fix;
>> >>> see http://lists.gnu.org/archive/html/dejagnu/201
Hi,
This patch add three intrinsics that are required by the ACLE specification.
A new testcase is added which covers vfms_n_f32 and vfmsq_n_f32. Tested on
both aarch64-linux-gnu and aarch64_be-linux-gnu.
OK?
Index: gcc/ChangeLog
===
On Thu, Dec 11, 2014 at 1:26 PM, Richard Sandiford
wrote:
> As pointed out in PR 64182, wide-int rounded division gets the
> ties-away-from-zero case wrong for odd-numbered dividends, while
> double_int gets the unsigned case wrong by unconditionally treating
> a dividend or remainder with the top
On Wed, Dec 10, 2014 at 1:18 PM, Martin Liška wrote:
> Hello.
>
> As suggested by Richard, I split compare_operand functions to various
> functions
> related to a specific comparison. Apart from that I added fast check for
> volatility flag that caused miscompilation mentioned in PR63569.
>
> Patc
On Tue, Sep 23, 2014 at 4:07 PM, Kyrill Tkachov wrote:
> Hi all,
>
> Some intrinsics had the wrong name (inconsistent with the NEON intrinsics
> spec). This patch fixes that and adds the vrndx_f32 and vrndxq_f32
> intrinsics that were missing.
> These map down to vrintx.f32 NEON instructions (d an
As pointed out in PR 64182, wide-int rounded division gets the
ties-away-from-zero case wrong for odd-numbered dividends, while
double_int gets the unsigned case wrong by unconditionally treating
a dividend or remainder with the top bit set as negative. As Jakub
says, the test used in double_int m
On Thu, Dec 11, 2014 at 11:31:06AM +0100, Dominik Vogt wrote:
> Just to make this clear: It's not something that *might* happen.
> It *does* happen on s390[x] which does not use libffi but the hand
> written code in makefunc_s390.S and makefuncgo_s390[x].go.
>
> The same may not happen when calli
On Thu, Dec 11, 2014 at 10:56 AM, Bin.Cheng wrote:
> On Wed, Dec 10, 2014 at 9:47 PM, Richard Biener
> wrote:
>> On Fri, Dec 5, 2014 at 1:15 PM, Bin Cheng wrote:
>>> Hi,
>>> Though PR62178 is hidden by recent cost change in aarch64 backend, the ivopt
>>> issue still exists.
>>>
>>> Current candi
Hi Jason,
I managed to reproduce this fault now.
and entered a bug tracker for it:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64265
any ideas how this patch could move the __tsan_func_entry into the loop?
Thanks
Bernd.
On Wed, 10 Dec 2014 00:10:07, Bernd Edlinger wrote:
>
> Hi Jason,
>
>>
Hi,
yesterday, while working on c++/60955 I noticed this comment and
wondered if for 5 we want to do the below. Certainly passes testing on
x86_64-linux.
Thanks,
Paolo.
///
2014-12-11 Paolo Carlini
* typeck.c (maybe_warn_about_useless_cast): Remove unnecessary
On Thu, 11 Dec 2014, Marek Polacek wrote:
> On Wed, Dec 10, 2014 at 08:11:02PM +0100, Marc Glisse wrote:
> > >+inline tree
> > >+any_integral_type_check (tree __t, const char *__f, int __l, const char
> > >*__g)
> > >+{
> > >+ if (!(INTEGRAL_TYPE_P (__t)
> > >+ || ((TREE_CODE (__t) == COMPLEX_T
On Thu, Dec 11, 2014 at 07:51:44PM +1030, Alan Modra wrote:
> On Thu, Dec 11, 2014 at 10:06:23AM +0100, Dominik Vogt wrote:
> > On s390x, the static chain register cannot be used for passing the
> > Go closure pointer to a function: According to the Abi, the
> > dynamic linker is allowed to destro
ze-at-ltrans): New flag.
/usr/local/gcc/gcc-20141211/gcc/testsuite/g++.dg/ipa/pr64059.C:56:1: internal
compiler error: Segmentation fault.
0x40df742f crash_signal.
../../gcc/toplev.c:358.
0x412f2c9f get_binfo_at_offset(tree_node*, long, tree_node*).
Hi all,
Attached patch adds new check (all blocks of 8 spaces are replaced with
tabs) to contrib/check_GNU_style.sh. It also changes the script to allow
reading patches from stdin and strengthens the "Dot, space, space, new
sentence." check.
Is this ok to commit?
-Y
>From c099086a7325d5feca286
Hi Christophe,
Sorry to bother you again. After my clarification email below are you now
happy for these patches to go in?
Kind Regards,
David Sherwood.
> -Original Message-
> From: David Sherwood [mailto:david.sherw...@arm.com]
> Sent: 27 November 2014 14:53
> To: 'Christophe Lyon'
> Cc
The following patch fixes the performance regression in PR42108
by allowing PRE and LIM to see the division (to - from) / step
in translating do loops executed unconditionally. This makes
them not care for the fact that step might be zero and thus
the division might trap.
This makes the runtime
Hi,
Case gcc.target/aarch64/ldp_stp_3.c test fails on aarch64-none-elf.
Instead of merging the loads into ldp it generates:
foo:
adrpx1, .LANCHOR0
add x1, x1, :lo12:.LANCHOR0
ldr w0, [x1, 4]
ldr w3, [x1, 20]
ldr w2, [x1, 32]
Hi,
As described both in the PR and patch comments, this patch fixes PR62151 by
setting right value to ELIM_I0/ELIM_I1 when distributing REG_DEAD notes from
i0/i1. It is said that distribute_notes had caused many bugs in the past.
I think it still has bug in it, as noted in the PR. This patch doe
On Thu, Dec 11, 2014 at 5:56 PM, Bin.Cheng wrote:
> On Wed, Dec 10, 2014 at 9:47 PM, Richard Biener
> wrote:
>> On Fri, Dec 5, 2014 at 1:15 PM, Bin Cheng wrote:
>>> Hi,
>>> Though PR62178 is hidden by recent cost change in aarch64 backend, the ivopt
>>> issue still exists.
>>>
>>> Current candid
On Wed, Dec 10, 2014 at 9:47 PM, Richard Biener
wrote:
> On Fri, Dec 5, 2014 at 1:15 PM, Bin Cheng wrote:
>> Hi,
>> Though PR62178 is hidden by recent cost change in aarch64 backend, the ivopt
>> issue still exists.
>>
>> Current candidate selecting algorithm tends to select fewer candidates give
Hi all,
While looking in this area on other business I noticed we could be using
the names R0_REGNUM
and R1_REGNUM when creating those REG rtxs since it's a bit more
descriptive that just 0 and 1.
Tested arm-none-eabi.
Ok for trunk?
Thanks,
Kyrill
2014-12-11 Kyrylo Tkachov kyrylo.tkac...
On 10/12/14 22:18, Mike Stump wrote:
On Dec 10, 2014, at 10:05 AM, Kyrill Tkachov wrote:
Thanks for the guidance. I've moved the definitions into a separate file and
included that in the places that use it (more than 2 places in my count). This
is the patch attached.
The second patch (will s
On Thu, Dec 11, 2014 at 10:06:23AM +0100, Dominik Vogt wrote:
> On s390x, the static chain register cannot be used for passing the
> Go closure pointer to a function: According to the Abi, the
> dynamic linker is allowed to destroy the contents of r0 (static
> chain register) eventually causing a
On Fri, Oct 10, 2014 at 01:42:40PM -0700, Richard Henderson wrote:
> The background here is my thread from last week[1], and Ian's reply[2],
> wherein he rightly points out that not needing to play games with
> mmap in order to implement closures for Go is a strong reason to
> continue using custom
On Wed, Dec 10, 2014 at 4:22 PM, Yuri Rumyantsev wrote:
> Richard,
>
> Thanks for your reply!
>
> I didn't understand your point:
>
> Well, I don't mind splitting all critical edges unconditionally
>
> but you do it unconditionally in proposed patch.
I don't mind means I am fine with it.
> Also
Dodji Seketeli wrote:
Manuel López-Ibáñez writes:
New version using XNEW. Bootstrapped & tested on x86_64-linux-gnu.
OK?
The diagnostics infrastructure changes are OK for me. Thanks!
And the Fortran part was already approved before. (Otherwise, take this
as another rubber stamp.)
Thanks
As discussed in Bugzilla.
Bootstrapped and tested.
Is it Ok to backport it to 4.9 branch, with _M_in_iterator kept unused?
Thanks! :)
--
Regards,
Tim Shen
commit 18c4399589b414c79c6e85ab91f7a95f2fcad829
Author: timshen
Date: Wed Dec 10 21:30:13 2014 -0800
PR libstdc++/64239
On Wed, Dec 10, 2014 at 08:11:02PM +0100, Marc Glisse wrote:
> >+inline tree
> >+any_integral_type_check (tree __t, const char *__f, int __l, const char
> >*__g)
> >+{
> >+ if (!(INTEGRAL_TYPE_P (__t)
> >+|| ((TREE_CODE (__t) == COMPLEX_TYPE
> >+ || VECTOR_TYPE_P (__t))
> >+&&
Tobias Burnus writes:
> 2014-12-06 Tobias Burnus
> Manuel L³pez-Ib¡±ez
>
> gcc/
> * diagnostic.c (get_terminal_width): Renamed from getenv_columns,
> removed static, and additionally use ioctl to get width.
> (diagnostic_set_caret_max_width): Update call.
>
Manuel López-Ibáñez writes:
> New version using XNEW. Bootstrapped & tested on x86_64-linux-gnu.
>
> OK?
The diagnostics infrastructure changes are OK for me. Thanks!
Cheers,
--
Dodji
89 matches
Mail list logo
