Hi,
PR85080 identifies a test case that started failing last year when
an improvement was made to the vectorizer. The failure turns out to
be appropriate. The test used to not expect the loop in the first
function to be vectorized, because the cost of potentially unaligned
loads made this unprof
On Apr 15, 2018, at 6:29 PM, Segher Boessenkool
wrote:
>
> On Sun, Apr 15, 2018 at 06:08:44PM -0500, Bill Schmidt wrote:
>> On Apr 15, 2018, at 5:50 PM, Jakub Jelinek wrote:
>>>
>>> On Sun, Apr 15, 2018 at 04:53:27PM -0500, Bill Schmidt wrote:
2018-04-15 Bill Schmidt
PR t
On Sun, Apr 15, 2018 at 06:08:44PM -0500, Bill Schmidt wrote:
> On Apr 15, 2018, at 5:50 PM, Jakub Jelinek wrote:
> >
> > On Sun, Apr 15, 2018 at 04:53:27PM -0500, Bill Schmidt wrote:
> >> 2018-04-15 Bill Schmidt
> >>
> >>PR testsuite/85326
> >>* g++.dg/undef-bool-1.C: New file.
> >
On Apr 15, 2018, at 5:50 PM, Jakub Jelinek wrote:
>
> On Sun, Apr 15, 2018 at 04:53:27PM -0500, Bill Schmidt wrote:
>> 2018-04-15 Bill Schmidt
>>
>> PR testsuite/85326
>> * g++.dg/undef-bool-1.C: New file.
>
> Tests really shouldn't be added to g++.dg/ directly, but to subdirector
On Sun, Apr 15, 2018 at 04:53:27PM -0500, Bill Schmidt wrote:
> 2018-04-15 Bill Schmidt
>
> PR testsuite/85326
> * g++.dg/undef-bool-1.C: New file.
Tests really shouldn't be added to g++.dg/ directly, but to subdirectories
thereof.
In this case, I think g++.dg/ext/undef-bool-1.C i
Hi,
This test fixes the part of PR85326 that involves powerpc test cases.
It removes support for .C tests in gcc.target/powerpc and moves the
one .C test from that directory to g++.dg with target constraints.
Tested on powerpc64le-linux-gnu. Okay for trunk?
Thanks,
Bill
[gcc/testsuite]
2018-0
I should mention that the x86_64 port has the same issue with mangling if you
use the -mlong-double-128 option, since __float128 and long double use the same
mangling.
--
Michael Meissner, IBM
IBM, M/S 2506R, 550 King Street, Littleton, MA 01460-6245, USA
email: meiss...@linux.vnet.ibm.com, phone
PR target/85075 shows that there are some problems with the types for the 3
128-bit floating point types on the PowerPC:
__float128 (and _Float128 in C, IEEE 128-bit)
__ieee128 (IBM extended double)
long double (either IEEE 128-bit or IBM extended double)
Wi
Replace ASM_OUTPUT_LABEL with fprintf so that internal labels in property
note section are unchanged -fleading-underscore.
OK for trunk?
H.J.
---
gcc/
PR target/85404
* config/i386/cet.c (file_end_indicate_exec_stack_and_cet):
Replace ASM_OUTPUT_LABEL with fprintf.
gcc/t
These tests must be compiled with -mno-cet/-mno-ibt/-mno-shstk.
OK for trunk?
H.J.
---
* c-c++-common/fcf-protection-1.c: Likewise.
* c-c++-common/fcf-protection-2.c: Likewise.
* c-c++-common/fcf-protection-3.c: Likewise.
* c-c++-common/fcf-protection-5.c: Likewise
These tests must be compiled with -fcf-protection=none -mno-cet.
OK for trunk?
H.J.
* c-c++-common/attr-nocf-check-1.c: Compile with
-fcf-protection=none -mno-cet for x86 targets.
* c-c++-common/attr-nocf-check-3.c: Likewise.
* gcc.dg/march-generic.c: Likewise
Define STACK_SAVEAREA_MODE to hold both shadow stack and stack pointers.
Replace builtin_setjmp_setup and builtin_longjmp with save_stack_nonlocal
and restore_stack_nonlocal to support both builtin setjmp/longjmp as well
as non-local goto in nested functions.
OK for trunk?
H.J.
gcc/
Since CET is applied to the whole program, it is correct to disallow
-fcf-protection=full without -mcet. But compiler shouldn't crash.
OK for trunk?
H.J.
gcc/
PR target/85403
* config/i386/i386.c (get_builtin_code_for_version): Check
error_mark_node.
gcc/testsuite/
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the Swedish team of translators. The file is available at:
http://translationproject.org/latest/gcc/sv.po
(This file, 'gcc-8.1-b20180401.sv.po',
14 matches
Mail list logo
