On Fri, Jan 12, 2018 at 09:53:28AM +0100, Richard Biener wrote:
> This fixes PR83157 (well, not the guality fail...) and avoids creating
> references to abstract instances that actually end up refering to
> the concrete instance thereby eventually picking up invalid location
> attributes (and
Ping.
FWIW, the SLP test failures it fixes were ICEs rather than code-quality
tests, so this is a correctness fix rather than an optimisation.
Thanks,
Richard
Richard Sandiford writes:
> The SVE support for the new CONST_VECTOR encoding needs to be able
> to
On 12 January 2018 at 10:25, Rainer Orth wrote:
> Hi Christophe,
>
>> On 10 January 2018 at 15:44, Jakub Jelinek wrote:
>>> On Mon, Oct 23, 2017 at 02:30:24PM +0200, Christophe Lyon wrote:
After Jakub's suggestion in PR82120 and PR81184, the
On Solaris, gcc has long failed to enable libc's C99 mode as documented
in PR target/40411. To do so, one needs to link with a values-xpg6.o
file provided by the system. That file defines a __xpg6 variable in a
way which lets libc (and in some cases libm) select between C99 and
non-C99 behaviour
Hi,
this patch adds dg-require-effective-target indirect_jumps for g++
test-cases.
Build and reg-tested on x86_64 and nvptx.
Committed as obvious.
Thanks,
- Tom
Add dg-require-effective-target indirect_jumps for g++
2018-01-12 Tom de Vries
*
Hi Christophe,
>> not at all, but it has two problems:
>>
>> * The new branch_cost effective-target keyword needs documenting in
>> sourcebuild.texi, as always.
>>
>
> Sorry, I keep forgetting this. How about the trivial attached patch? (I'm
> mainly
> asking to check I add it to the most
kewise.
2018-01-12 Eric Botcazou <ebotca...@adacore.com>
* gcc.c-torture/execute/20180112-1.c: New test.
--
Eric BotcazouIndex: rtlanal.c
===
--- rtlanal.c (revision 256562)
+++ rtlanal.c (working copy)
@@ -44
Hi Nathan,
>> On 01/02/2018 09:36 AM, Marek Polacek wrote:
>>> This test exercising inheriting a template constructor in this PR got
>>> fixed with
>>> r251426. As I don't see any lambdas here, I thought it worth to add it.
>>>
>>> Tested on x86_64-linux, ok for trunk?
>>>
>>> 2018-01-02 Marek
On Fri, Jan 12, 2018 at 10:12:15AM +0100, Rainer Orth wrote:
> Hi Nathan,
>
> >> On 01/02/2018 09:36 AM, Marek Polacek wrote:
> >>> This test exercising inheriting a template constructor in this PR got
> >>> fixed with
> >>> r251426. As I don't see any lambdas here, I thought it worth to add it.
On Fri, 12 Jan 2018, Richard Biener wrote:
>
> This fixes PR83157 (well, not the guality fail...) and avoids creating
> references to abstract instances that actually end up refering to
> the concrete instance thereby eventually picking up invalid location
> attributes (and whatever else there
On Fri, 12 Jan 2018, Jakub Jelinek wrote:
> On Fri, Jan 12, 2018 at 09:16:35AM +0100, Richard Biener wrote:
> > Or another workaround would be to make sure non-constant sizepos
> > stay non-constant by doing sth like the following? FEs can mark
> > expressions as TREE_CONSTANT if they don't want
Hi Christophe,
> On 10 January 2018 at 15:44, Jakub Jelinek wrote:
>> On Mon, Oct 23, 2017 at 02:30:24PM +0200, Christophe Lyon wrote:
>>> After Jakub's suggestion in PR82120 and PR81184, the attached patch
>>> adds the -mbranch-cost option to the ARM target. My understanding
Hi,
this patch adds dg-require-effective-target alloca for c++ test-cases.
Build and reg-tested on x86_64 and nvptx.
Committed as obvious.
Thanks,
- Tom
Add dg-require-effective-target alloca for c++ test-cases
2018-01-12 Tom de Vries
* c-c++-common/dwarf2/vla1.c:
On Wed, 10 Jan 2018, Martin Jambor wrote:
> Hello,
>
> I would really like to ping the FMA transformation prevention patch that
> I sent here in December, which, after incorporating a suggestion from
> Richi, re-base and re-testing, I re-post below. I really think that it
> should make into gcc
Of course it would be helpful, if I included the patch:
2018-01-12 Michael Meissner
* config.gcc (powerpc*-linux*-*): Add support for 64-bit little
endian Linux systems to optionally enable multilibs for selecting
the long double type if
On Fri, Jan 12, 2018 at 9:10 AM, marxin wrote:
> Hi.
>
> Due to changes to qsort where Alexander added new implementation in vec.c,
> we need to change Makefile.in. Apart from that qsort_chk triggers errors
> for current implementation of compare function. That's also fixed.
>
This fixes a somewhat obscure interaction between alloca and setjmp/longjmp in
PIC mode on the SPARC architecture. The problem is that the canonical PIC
register on SPARC (%l7) is call-saved like on other architectures but, unlike
on other architectures, not (always) preserved by setjmp.
It has some problems running on some 64-bit configuratiions, and the
bug it is testing for is only on 32-bit; so let's not run it elsewhere.
Committing to trunk.
Segher
2018-01-12 Segher Boessenkool
gcc/testsuite/
PR target/83629
*
> On 19 Dec 2017, at 16:27, Jeff Law wrote:
>
> On 12/19/2017 03:12 AM, Alan Hayward wrote:
>> Ping ping.
>> I think there should be enough information in the first test to show that
>> any "set to self”
>> registers become live. Let me know if there’s anything I’ve missed.
>
Hi,
On Thu, Jan 11 2018, Jeff Law wrote:
> On 01/07/2018 03:59 PM, H.J. Lu wrote:
>> Add -mindirect-branch-loop= option to control loop filler in call and
>> return thunks generated by -mindirect-branch=. 'lfence' uses "lfence"
>> as loop filler. 'pause' uses "pause" as loop filler. 'nop' uses
On 01/12/2018 08:09 AM, Kumar, Venkataramanan wrote:
> Hi all,
>
>> -Original Message-
>> From: Kumar, Venkataramanan
>> Sent: Friday, January 12, 2018 8:16 PM
>> To: 'H.J. Lu' ; Martin Jambor
>> Cc: Nagarajan, Muthu kumar raj
Sorry, just realised this wasn't ACKed
Jeff Law writes:
> On 11/17/2017 02:36 AM, Richard Sandiford wrote:
>> Richard Sandiford writes:
>>> This patch adds support for vectorising groups of IFN_MASK_LOADs
>>> and IFN_MASK_STOREs using conditional
On January 12, 2018 4:47:41 PM GMT+01:00, Jakub Jelinek
wrote:
>On Fri, Jan 12, 2018 at 10:25:30AM +0100, Richard Biener wrote:
>> On Fri, 12 Jan 2018, Jakub Jelinek wrote:
>>
>> > On Fri, Jan 12, 2018 at 09:16:35AM +0100, Richard Biener wrote:
>> > > Or another workaround
Hello!
It turns out that without ashlsi3 named pattern combine pass won't
simplify subregs in:
(set (reg:SI 74)
(plus:SI (subreg:SI (ashift:DI (reg:DI 17 $17 [ b ])
(const_int 2 [0x2])) 0)
(reg:SI 16 $16 [ a ])))
Attached patch adds relevant insn-and-split patterns
On Thu, Jan 11, 2018 at 10:17 PM, H.J. Lu wrote:
> On Thu, Jan 11, 2018 at 11:07 AM, Uros Bizjak wrote:
>> On Wed, Jan 10, 2018 at 9:40 PM, H.J. Lu wrote:
>>> When a function call is removed, it may become a leaf function. But if
On Fri, Jan 12, 2018 at 05:45:15PM +0100, Richard Biener wrote:
> >In a few C testcases the cases with TREE_CONSTANT before gimplify_expr
> >are
> >stuff like:
> >extern void dynreplace_trampoline(void);
> >extern void dynreplace_trampoline_endlabel(void);
> >int dynreplace_add_trampoline(void)
>
Hi
This patch fixes my earlier test case that fails for arm-none-eabi
with explicit user option for -mfloat-abi which conflict with
the test case options. I have added a guard to skip the test
on those cases.
@Christophe:
Sorry about this. I think this should fix the test case.
Can you please
James Greenhalgh writes:
> On Sat, Jan 06, 2018 at 07:13:22PM +, Richard Sandiford wrote:
>> James Greenhalgh writes:
>> > On Fri, Nov 03, 2017 at 05:50:54PM +, Richard Sandiford wrote:
>> >> This patch adds gcc.target/aarch64 tests for
On Fri, Jan 12, 2018 at 10:25:30AM +0100, Richard Biener wrote:
> On Fri, 12 Jan 2018, Jakub Jelinek wrote:
>
> > On Fri, Jan 12, 2018 at 09:16:35AM +0100, Richard Biener wrote:
> > > Or another workaround would be to make sure non-constant sizepos
> > > stay non-constant by doing sth like the
> On Fri, Jan 12, 2018 at 12:01 AM, Uros Bizjak wrote:
> > On Thu, Jan 11, 2018 at 2:28 PM, H.J. Lu wrote:
> >
> >> Hi Uros,
> >>
> >> Can you take a look at my x86 backend changes so that they are ready
> >> to check in once we have consensus.
> >
> >
On 12/01/18 14:18 +0100, Torvald Riegel wrote:
On Tue, 2018-01-09 at 17:54 +, Mike Crowe wrote:
On Tuesday 09 January 2018 at 13:50:54 +, Jonathan Wakely wrote:
> On 07/01/18 20:55 +, Mike Crowe wrote:
> > The futex system call supports waiting for an absolute time if
> >
The following patch fixes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80481
During forming an allocation thread in a multi-region function a
conflict allocno was added to the thread and that resulted in generation
of additional moves. The patch prevents inclusion of conflict allocnos
On Fri, Jan 12, 2018 at 6:50 AM, Jan Hubicka wrote:
>> On Fri, Jan 12, 2018 at 12:01 AM, Uros Bizjak wrote:
>> > On Thu, Jan 11, 2018 at 2:28 PM, H.J. Lu wrote:
>> >
>> >> Hi Uros,
>> >>
>> >> Can you take a look at my x86 backend changes
On 10/01/18 23:26, Jeff Law wrote:
> On 01/08/2018 09:01 AM, Bill Schmidt wrote:
>> On Jan 8, 2018, at 8:06 AM, Richard Earnshaw (lists)
>> wrote:
>>>
>>> On 08/01/18 02:20, Bill Schmidt wrote:
Hi Richard,
Unfortunately, I don't see any way that this will
-mstring is only enabled by default on 601, and with -Os on some
configurations. It is almost always slower (than not using it) and
does not very often lead to smaller code.
This patch disables it. If a user uses -mstring he gets a warning
(but not with -mno-string). I left the target
On 01/11/2018 11:44 PM, Prathamesh Kulkarni wrote:
On 12 January 2018 at 06:15, Martin Sebor wrote:
On 01/11/2018 02:48 PM, Rainer Orth wrote:
Hi Martin,
I am not sure why constant string is not emitted for arm-linux-gnueabihf
?
As far as this issue is concerned, should I
Hi all,
> -Original Message-
> From: Kumar, Venkataramanan
> Sent: Friday, January 12, 2018 8:16 PM
> To: 'H.J. Lu' ; Martin Jambor
> Cc: Nagarajan, Muthu kumar raj ;
> GCC Patches ; Jeff Law
Joseph Myers wrote:
> No existing glibc version defines math_errhandling based on
> __NO_MATH_ERRNO__. I'd expect such a change to come with a glibc patch,
> and indeed a GCC execution test of the value of math_errhandling to make
> sure the compiler's behavior isn't contradicting what's
Hi!
The LTO debug changes create a DW_TAG_subprogram in main in one spot and
a small DW_TAG_subprogram that has DW_AT_abstract_origin to that +
DW_AT_ranges when doing hot/cold partitioning. Unfortunately, it seems GDB
in that case doesn't read the DIE in the initial debug info read, as
On 01/12/2018 07:05 AM, H.J. Lu wrote:
> On Fri, Jan 12, 2018 at 4:38 AM, Martin Jambor wrote:
>> Hi,
>>
>> On Thu, Jan 11 2018, Jeff Law wrote:
>>> On 01/07/2018 03:59 PM, H.J. Lu wrote:
Add -mindirect-branch-loop= option to control loop filler in call and
return
On Thu, Jan 11, 2018 at 3:00 PM, H.J. Lu wrote:
> On Thu, Jan 11, 2018 at 2:46 PM, Jeff Law wrote:
>> Do you want to mention that CET and retpolines are inherently
>
> I will document it.
>
>> incompatible? Should an attempt to use them together generate a
On Fri, Jan 12, 2018 at 2:47 PM, Richard Sandiford
wrote:
> The idea with the main 107-patch poly_int series (latterly 109-patch)
> was to change the mode sizes and vector element counts to poly_int and
> then propagate those changes as far as they needed to go to
Hi all,
> -Original Message-
> From: H.J. Lu [mailto:hjl.to...@gmail.com]
> Sent: Friday, January 12, 2018 7:36 PM
> To: Martin Jambor
> Cc: Nagarajan, Muthu kumar raj ;
> Kumar, Venkataramanan ; GCC
>
Hi!
In 7.x and earlier, decl_constant_value_for_optimization punted if
the initializer has ARRAY_TYPE or BLKmode type, and the following patch
shows that is reasonable thing to do, otherwise we might grab very large
initializers out of constant variable initializers and if e.g. ARRAY_REF
on it
On January 12, 2018 4:52:27 PM GMT+01:00, Jakub Jelinek
wrote:
>Hi!
>
>The LTO debug changes create a DW_TAG_subprogram in main in one spot
>and
>a small DW_TAG_subprogram that has DW_AT_abstract_origin to that +
>DW_AT_ranges when doing hot/cold partitioning. Unfortunately,
> gcc/
>
> * config/i386/i386-opts.h (indirect_branch): New.
> * config/i386/i386-protos.h (ix86_output_indirect_jmp): Likewise.
> * config/i386/i386.c (ix86_using_red_zone): Disallow red-zone
> with local indirect jump when converting indirect call and jump.
>
> Add 'V', a special modifier which prints the name of the full integer
> register without '%'. For
>
> extern void (*func_p) (void);
>
> void
> foo (void)
> {
> asm ("call __x86_indirect_thunk_%V0" : : "a" (func_p));
> }
>
> it generates:
>
> foo:
> movqfunc_p(%rip), %rax
>
Hi HJ,
> -Original Message-
> From: Kumar, Venkataramanan
> Sent: Friday, January 12, 2018 8:39 PM
> To: 'H.J. Lu' ; 'Martin Jambor'
> Cc: Nagarajan, Muthu kumar raj ;
> 'GCC Patches' ; 'Jeff
Hi,
On 12/01/2018 19:13, Jason Merrill wrote:
Hmm, I think dropping the attributes is reasonable for grokdeclarator
to do as error-recovery, similarly to how it discards an ill-formed
exception-specification. But let's assert seen_error() in that case.
Agreed. The below passes testing.
On Thu, Jan 11, 2018 at 01:36:53PM -0600, Bill Seurer wrote:
> [PATCH, rs6000] pr58684, pr83759 Disable test cases that fail on powerpc64.
>
> This patch disables a few test cases on powerpc64 that fail after r256380
> due to a longstanding issue with floating-point compares.
>
> See
On Fri, Jan 12, 2018 at 10:00 AM, Jan Hubicka wrote:
>> Add 'V', a special modifier which prints the name of the full integer
>> register without '%'. For
>>
>> extern void (*func_p) (void);
>>
>> void
>> foo (void)
>> {
>> asm ("call __x86_indirect_thunk_%V0" : : "a"
On 01/12/2018 11:23 AM, Segher Boessenkool wrote:
On Thu, Jan 11, 2018 at 01:36:53PM -0600, Bill Seurer wrote:
[PATCH, rs6000] pr58684, pr83759 Disable test cases that fail on powerpc64.
This patch disables a few test cases on powerpc64 that fail after r256380
due to a longstanding issue with
On Thu, Jan 11, 2018 at 01:11:05PM -0500, Michael Meissner wrote:
> In working on the transition of PowerPC long double from using the IBM
> extended
> double format to IEEE 128-bit floating point, I noticed that the long double
> .gnu_attribute (#4) was not set if the compiler can handle long
Hi,
atm, for nvptx we have the following failure:
...
FAIL: gcc.dg/stdint-width-1.c (test for excess errors)
...
In more detail:
...
gcc/testsuite/gcc.dg/stdint-width-1.c:20:4: error: #error "missing
INT8_WIDTH"
...
The test fails because newlib's stdint.h lacks TS 18661-1 support.
The test
On Fri, 12 Jan 2018, Rainer Orth wrote:
> At the same time, I had a new look at when values-Xc.o is used by the
> Studio compilers. It selects strict ISO C mode in a couple of cases,
> and the latest Studio 12.6 cc, which is about to do away with the
> previous -Xc option which enabled that mode
On Fri, 12 Jan 2018, Wilco Dijkstra wrote:
> I've updated the patch to exclude pre-C99 C/C++/ObjC:
Another question to consider: what about configurations (mostly
soft-float) where floating-point exceptions are not supported? (glibc
wrongly defines math_errhandling to include MATH_ERREXCEPT
On Thu, Jan 11, 2018 at 5:11 PM, Paolo Carlini wrote:
> On 11/01/2018 21:33, Jason Merrill wrote:
>> On 01/10/2018 06:50 PM, Paolo Carlini wrote:
>>>
>>> thus the below is a rather "dull" solution at the level of
>>> cplus_decl_attributes itself:
On Thu, Jan 04, 2018 at 10:31:16PM +0100, Jakub Jelinek wrote:
> While debugging PR target/83554, I first thought the bug is that
> regrename creates a new raw REG each time and when the insn uses
> match_dup that it would be a problem.
>
> While that is not the case, for match_dup we actually
In working on pr83160 I came across some code to cleanup
1) name mark_rvalue_use's final parm to remind us what it is
2) fix poor line breaking in convert_like_real
3) move mark_lvalue_use{,_nonread) close to their friend mark_rvalue_use
applying to trunk.
nathan
--
Nathan Sidwell
2018-01-12
Hi DJ,
>>Do you have checkin privs yet?
I have filled out the form. "Thanks for your request. It must be approved by
the person you named as approver ...
>> This is ok aside from..
Sorry about this. I will keep this in mind in future.
I corrected the patch with your second suggestion.
Best
Complex Partial Integers are unimplemented, resulting in an ICE when
attempting to use them. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79242
This results in GCC7/8 for msp430-elf failing to build.
typedef _Complex __int20 C;
C
foo (C x, C y)
{
return x + y;
}
(Thanks Jakub -
On Fri, Jan 12, 2018 at 11:22 AM, Segher Boessenkool
wrote:
> -mstring is only enabled by default on 601, and with -Os on some
> configurations. It is almost always slower (than not using it) and
> does not very often lead to smaller code.
>
> This patch disables it.
> > Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
> >
> > 2018-01-04 Jakub Jelinek
> >
> > * regrename.c (regrename_do_replace): If replacing the same
> > reg multiple times, try to reuse last created gen_raw_REG.
>
> I'd like to ping this
On Fri, Jan 12, 2018 at 10:38:39AM -0700, Jeff Law wrote:
> >>> Thanks for pointing it out. I see it there as well with
> >>> Prathamesh's test case, though not with the test case in
> >>> bug 83543. It is the same root cause in both. I agree
> >>> that enhancing the strlen pass to handle this
> Add -mfunction-return= option to convert function return to call and
> return thunks. The default is 'keep', which keeps function return
> unmodified. 'thunk' converts function return to call and return thunk.
> 'thunk-inline' converts function return to inlined call and return thunk.
>
On Fri, 12 Jan 2018, Torvald Riegel wrote:
> Another option might be to require a minimum glibc version on Linux, and
> build libstdc++ for that. That would yield a minimum kernel version as
> well, and we may can make use of other things in return such as syscall
> wrappers.
A minimum glibc
On 01/11/2018 04:07 PM, Jakub Jelinek wrote:
> On Thu, Jan 11, 2018 at 03:46:51PM -0700, Jeff Law wrote:
>> Note I'm expecting Uros to chime in. So please do not consider this
>> ack'd until you hear from Uros.
>>
>> At a high level is there really that much value in having thunks in the
>>
On Fri, Dec 29, 2017 at 12:35:03AM -0500, Michael Meissner wrote:
> * gcc.target/powerpc/float128-hw7.c: Likewise.
> --- gcc/testsuite/gcc.target/powerpc/float128-hw7.c (nonexistent)
> +++ gcc/testsuite/gcc.target/powerpc/float128-hw7.c (working copy)
> @@ -0,0 +1,27 @@
> +/* { dg-do
On Fri, Jan 12, 2018 at 07:23:37AM -0500, Michael Meissner wrote:
> Of course it would be helpful, if I included the patch:
Yup :-)
> 2018-01-12 Michael Meissner
>
> * config.gcc (powerpc*-linux*-*): Add support for 64-bit little
> endian Linux
Hi!
On Fri, Jan 12, 2018 at 01:46:27AM -0500, Michael Meissner wrote:
> This is my current multilib version support for migrating PowerPC servers from
> using IBM extended double as the long double type to IEEE 128-bit floating
> point.
>
> I have built both little endian and big endian PowerPC
On Wed, Jan 10, 2018 at 3:35 PM, Dominique d'Humières
wrote:
> Hi Janne,
>
> With this patch, bootstrap fails with
>
> ../../work/gcc/fortran/array.c: In function 'bool
> gfc_resolve_character_array_constructor(gfc_expr*)':
> ../../work/gcc/fortran/array.c:2062:36:
Hi!
After the addition of location wrappers the
targetm.resolve_overloaded_builtin target hook is called with parameters
that may have those location wrappers in it. Seems generic code has been
changed to fold_for_warn fold it away when looking for something that should
be e.g. INTEGER_CST.
On Fri, 2018-01-12 at 09:07 +0100, Markus Trippelsdorf wrote:
> On 2018.01.11 at 18:21 -0500, David Malcolm wrote:
> > diff --git a/gcc/testsuite/g++.dg/wrappers/pr83799.C
> > b/gcc/testsuite/g++.dg/wrappers/pr83799.C
> > new file mode 100644
> > index 000..f93c0ae
> > --- /dev/null
> > +++
On 01/12/2018 09:23 AM, Martin Sebor wrote:
> On 01/11/2018 11:44 PM, Prathamesh Kulkarni wrote:
>> On 12 January 2018 at 06:15, Martin Sebor wrote:
>>> On 01/11/2018 02:48 PM, Rainer Orth wrote:
Hi Martin,
>> I am not sure why constant string is not emitted
Hello,
The below patch fixes 31 regression failures (28 for C and 3 for C++, see
below) plus the problem discovered here
https://gcc.gnu.org/ml/gcc-patches/2018-01/msg00688.html by DJ.
Tested with the following command:
make -k check-gcc RUNTESTFLAGS=--target_board=rl78-sim
List of previous
Le 12 janv. 2018 15:26, "Sudakshina Das" a écrit :
Hi
This patch fixes my earlier test case that fails for arm-none-eabi
with explicit user option for -mfloat-abi which conflict with
the test case options. I have added a guard to skip the test
on those cases.
@Christophe:
If we're going to try to do normal semantic checking of static_cast in
a template, we need to use build_non_dependent_expr like we do for
function calls.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit 4d7e6ada4e9f1c83d59b0e83d7e554ddae5cb3a8
Author: Jason Merrill
Date:
On Power 7 and Power 8 little endian, the code generator has been
emitting two instructions for each vector load and each vector store.
One instruction does a swapping load or store, and the second
instruction does an in-register swap.
This patch replaces the two-instruction sequences with a
On Thu, Jan 11, 2018 at 05:35:59PM -0500, Michael Meissner wrote:
> On Wed, Jan 10, 2018 at 11:48:30PM +, Joseph Myers wrote:
> > On Wed, 10 Jan 2018, Michael Meissner wrote:
> >
> > > This patch is next in my series of patches to enable us to configure the
> > > long
> > > double type on
On Fri, Jan 12, 2018 at 10:57:08AM -0700, Jeff Law wrote:
> On 01/11/2018 04:07 PM, Jakub Jelinek wrote:
> > On Thu, Jan 11, 2018 at 03:46:51PM -0700, Jeff Law wrote:
> >> Note I'm expecting Uros to chime in. So please do not consider this
> >> ack'd until you hear from Uros.
> >>
> >> At a high
> Add -mindirect-branch-register to force indirect branch via register.
> This is implemented by disabling patterns of indirect branch via memory,
> similar to TARGET_X32.
>
> -mindirect-branch= and -mfunction-return= tests are updated with
> -mno-indirect-branch-register to avoid false test
"Sebastian Perta" writes:
> Please let me know if this is OK. Thank you!
Do you have checkin privs yet?
This is ok aside from..
> + /* 'dead' keeps track of the QImode registers if r is of different size
> + we need to check the other subparts as well */
Jason,
this fixes 83160, where we complain about not having an lvalue in things
like:
void foo () {
const int a = 0;
[] () {
const int = a; // here
};
}
The problem is that we in convert_like_real we have ref_bind->identity
conversions, and the identity conversion calls
On Fri, Jan 12, 2018 at 10:27 AM, Kumar, Venkataramanan
wrote:
> Hi HJ,
>
>> -Original Message-
>> From: Kumar, Venkataramanan
>> Sent: Friday, January 12, 2018 8:39 PM
>> To: 'H.J. Lu' ; 'Martin Jambor'
>> Cc:
Hi,
Add support for gimple folding of the mergeh, mergel intrinsics.
Since the merge low and merge high variants are almost identical, a
new helper function has been added so that code can be shared.
This also adds define_insn for xxmrghw, xxmrglw instructions, allowing us
to generate xxmrglw
On 12/21/2017 11:59 PM, Sebastian Huber wrote:
> On 21/12/17 05:58, Jeff Law wrote:
>> On 08/22/2017 11:15 PM, Sebastian Huber wrote:
>>> Hello Jeff,
>>>
>>> On 03/08/17 07:11, Sebastian Huber wrote:
On 02/08/17 21:30, Jeff Law wrote:
> On 07/24/2017 12:03 AM, Sebastian Huber wrote:
This fixes PR 83601.
Tested on x86_64-linux-gnu.
--
Regards,
Tim Shen
commit 01a85ea3ae77acc7ad03430a6982db1b2b8c8bc3
Author: Tim Shen
Date: Fri Jan 12 22:22:45 2018 -0800
PR libstdc++/83601
* include/bits/regex.tcc (regex_replace): Fix escaping
Hi All,
> -Original Message-
> From: H.J. Lu [mailto:hjl.to...@gmail.com]
> Sent: Saturday, January 13, 2018 1:11 AM
> To: Kumar, Venkataramanan
> Cc: Nagarajan, Muthu kumar raj ;
> GCC Patches ;
Joseph Myers writes:
> Contrary to a previous review, you should *not* be removing RejectNegative
> from -fdebug-prefix-map=, and should be including it on both the new
> options. [...]
>
> The patch is OK with that fixed.
Thanks for finding the time to review this
On Fri, Jan 12, 2018 at 01:55:26PM -0600, Kelvin Nilsen wrote:
> On Power 7 and Power 8 little endian, the code generator has been
> emitting two instructions for each vector load and each vector store.
> One instruction does a swapping load or store, and the second
> instruction does an
On Fri, Jan 12, 2018 at 09:23:49PM +0100, Jakub Jelinek wrote:
> After the addition of location wrappers the
> targetm.resolve_overloaded_builtin target hook is called with parameters
> that may have those location wrappers in it. Seems generic code has been
> changed to fold_for_warn fold it
Ping in advance of stage 3 closing:
https://gcc.gnu.org/ml/gcc-patches/2018-01/msg00680.html
(As the majority of the strlen issues I raised recently, this
one also came out of my testing of the -Wrray-bounds and
-Wrestrict warnings newly enhanced in GCC 8.)
On 01/09/2018 02:41 PM, Martin
PR c++/83814 reports an ICE introduced by the location wrapper patch
(r256448), affecting certain memset calls within templates.
The issue occurs when fold_for_warn is called on the arguments to the
memset before they've been type-checked, leading to e.g. this assertion
failing within
On 09/01/18 21:51 +, Jonathan Wakely wrote:
This fixes unique_ptr so it doesn't print as unique_ptr, and
fixes a problem in the type-printers that can result in a gdb.error
exception (see https://sourceware.org/PR22686).
PR libstdc++/80276
*
On Tue, 9 Jan 2018, Boris Kolpackov wrote:
> Hi,
>
> Looks like this is the last chance for this patch to make GCC 8
> so I would like to ping it one last time:
>
> https://gcc.gnu.org/ml/gcc-patches/2017-11/msg01451.html
Contrary to a previous review, you should *not* be removing
On 12/21/2017 02:25 PM, Qing Zhao wrote:
> Hi,
>
> I updated my patch based on all your comments.
>
> the major changes are the following:
>
> 1. replace the candidate calls with __builtin_str(n)cmp_eq instead of
> __builtin_memcmp_eq;
> in builtins.c, when expanding the
On 01/12/2018 06:31 AM, Richard Sandiford wrote:
> Richard Sandiford writes:
>> Jeff Law writes:
>>> On 01/09/2018 11:39 AM, Richard Sandiford wrote:
This patch generalises various places that used hwi tree accessors
so that they can
On Fri, 12 Jan 2018, Jeff Law wrote:
> > What is the status of this PR
> >
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61152
> >
> > now? Can it be closed with a notice that this must be decided file by file?
> Seems reasonable with a note that it needs to be decided file by file.
And the
Hi!
Apparently Linux kernel contains various UB code that has been worked around
through -fno-strict-overflow in 7.x and before, but when
POINTER_TYPE_OVERFLOW_UNDEFINED has been removed it now fails to boot.
The following patch follows the comments in the PR, essentially reverts
Bin's removal
From: Cory Fields
Related to PR82407.
These two unstable sorts caused bootstrap comparison failures when crossing
from glibc to musl.
I'm not 100% sure about the correctness of the fixes, but I can verify that
when applied, bootstrap is successful.
Cory Fields (2):
Fix
1 - 100 of 151 matches
Mail list logo