On December 1, 2017 11:36:19 PM GMT+01:00, Jakub Jelinek
wrote:
>Hi!
>
>The bswap infrastructure uses the vuse field to make sure all the loads
>are
>having the same gimple_vuse and also uses it in bswap_replace.
>When this infrastructure is used inside of the store-merging pass, the
>problem is
On December 2, 2017 1:14:03 AM GMT+01:00, Jakub Jelinek
wrote:
>Hi!
>
>The following testcase shows that chkp_compute_bounds_for_assignment
>should know about POINTER_DIFF_EXPR and handle it like it used
>to handle MINUS_EXPR of 2 pointers in the past.
>
>Bootstrapped/regtested on x86_64-linux an
On December 2, 2017 1:14:10 AM GMT+01:00, Jakub Jelinek
wrote:
>Hi!
>
>With -fsanitize=return, we add __builtin_ubsan_handle_missing_return
>instead of __builtin_unreachable with BUILTINS_LOCATION locus,
>the following patch teaches warn function return pass to handle that
>too.
>
>Bootstrapped/r
On December 2, 2017 1:14:15 AM GMT+01:00, Jakub Jelinek
wrote:
>Hi!
>
>In TYPE_MODE we have a hack for vector types where we dynamically
>adjust it based on whether it is used from a function where the vector
>mode
>is or isn't supported (depending on target attribute, function
>multiversioning,
On 02 Dec 01:13, Jakub Jelinek wrote:
> On Fri, Dec 01, 2017 at 02:54:28PM +0100, Jakub Jelinek wrote:
> > Will try this:
>
> That failed to bootstrap, but here is an updated version that passed
> bootstrap/regtest on x86_64-linux and i686-linux, ok for trunk?
Great. OK.
--
Thanks, K
Committing as obvious and trivial.
Segher
2017-12-01 Segher Boessenkool
* doc/invoke.texi (-dp): Say that instruction cost is printed as well.
---
gcc/doc/invoke.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
inde
This patch to libgo exports the cgoCheck functions. The functions
cgoCheckPointer and cgoCheckResult are called by code generated by
cgo. That means that we need to export them using go:linkname, as
otherwise they are local symbols. The cgo code currently uses weak
references to only call the symb
The GCC middle-end has started emitting "control reaches end of
non-void function" warnings. This are not too useful for Go, which
implements its own error for this in the frontend. Avoid the
middle-end warnings for Go by 1) marking the builtin function panic
and the compiler-generated function __
I noticed a stray DWARF_DEBUG reference. The DWARF1 support was removed in
2004. So I did a quick find|grep and I found two more. This patch removes
them.
This was tested with quick x86_64-linux and mips-wrs-vxworks builds just to
verify that they still build, and by hand checking the docs to m
Hi!
The following testcase shows that chkp_compute_bounds_for_assignment
should know about POINTER_DIFF_EXPR and handle it like it used
to handle MINUS_EXPR of 2 pointers in the past.
Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
2017-12-01 Jakub Jelinek
* tree
Hi!
As the testcase shows, we weren't diagnosing the foo case in the testcase
and would just silently overwrite old DECL_INITIAL with error_mark_node
and ICE later on. Fixed thusly, bootstrapped/regtested on x86_64-linux
and i686-linux, ok for trunk?
2017-12-01 Jakub Jelinek
PR c++/8
Hi!
With -fsanitize=return, we add __builtin_ubsan_handle_missing_return
instead of __builtin_unreachable with BUILTINS_LOCATION locus,
the following patch teaches warn function return pass to handle that too.
Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
2017-12-01 Jakub
Hi!
In TYPE_MODE we have a hack for vector types where we dynamically
adjust it based on whether it is used from a function where the vector mode
is or isn't supported (depending on target attribute, function
multiversioning, etc.), but we don't have anything like that in DECL_MODE.
The following
On Fri, Dec 01, 2017 at 02:54:28PM +0100, Jakub Jelinek wrote:
> Will try this:
That failed to bootstrap, but here is an updated version that passed
bootstrap/regtest on x86_64-linux and i686-linux, ok for trunk?
2017-12-01 Jakub Jelinek
* config/i386/i386-protos.h (standard_sse_const
On Fri, 2017-12-01 at 22:56 +0100, Jakub Jelinek wrote:
> On Fri, Dec 01, 2017 at 04:48:20PM -0500, David Malcolm wrote:
> > PR c/83236 reports an issue where the C FE unhelpfully suggests the
> > use
> > of glibc's private "__ino_t" type when it fails to recognize
> > "ino_t":
> >
> > $ cat > tes
On Fri, Dec 01, 2017 at 12:40:22AM -0500, Michael Meissner wrote:
> After committing the previous patch, I noticed that it was now generating
> warnings for __{mul,div}kc3_{sw,hw} not having a prototype that I hadn't
> noticed during development of the patch. This is due to the fact that before
>
On Thu, Nov 30, 2017 at 05:49:27PM -0700, Jeff Law wrote:
> I think length and costing information are definitely things we want to
> include. Length is less of an issue now than it was in the past, but it
> definitely has value.
At least for risc targets length is usually pretty boring, but this
On Fri, Dec 01, 2017 at 05:33:39PM -0600, Segher Boessenkool wrote:
> Hi!
>
> On Thu, Nov 30, 2017 at 04:52:44PM -0500, Michael Meissner wrote:
> > No, then it tends to generate worse code if it is done before the first
> > split
> > pass (because it no longer keeps the address together). I've b
Hi!
On Thu, Nov 30, 2017 at 04:52:44PM -0500, Michael Meissner wrote:
> No, then it tends to generate worse code if it is done before the first split
> pass (because it no longer keeps the address together). I've been thinking
> that in general, we should replace these calls with a new predicate
This patch to the Go frontend by Than McIntosh adds a new control
variable to the Gogo class that stores the size threshold for nil
checks. This value can be used to control the policy for deciding when
a given deference operation needs a check and when it does not. A size
threshold of -1 means tha
Hi Will,
> On Dec 1, 2017, at 3:43 PM, Will Schmidt wrote:
>
> On Fri, 2017-12-01 at 18:46 +0100, Richard Biener wrote:
>> On December 1, 2017 6:22:21 PM GMT+01:00, Will Schmidt
>> wrote:
>>> Hi,
>>> Add support for folding of vec_msum in GIMPLE.
>>>
>>> This uses the DOT_PROD_EXPR gimple op,
I've come up with some patches that fix PR preprocessor/83173, which I reported
a couple of weeks ago.
The first patch is a test case. The second and third patches are two versions
of the fix. The first version is simpler, but it may still leave in place some
subtle incorrect behavior that happe
On Thu, Nov 30, 2017 at 12:54:53PM -0500, Michael Meissner wrote:
> On Thu, Nov 30, 2017 at 11:59:37AM +, Segher Boessenkool wrote:
> > This improves the output for load and store fusion a little. In most
> > cases it removes the comment output, because that makes the generated
> > assembler c
Hi!
On Thu, Nov 30, 2017 at 10:55:04AM -0700, Martin Sebor wrote:
> >Or, for that matter, what "length" means? Could be byte-length, sure.
> >But OTOH, for a RISC target it's always four, so why print it? The GCC
> >developers surely meant cycle-length with that, nothing else makes sense.
>
> H
Hi Aaron,
On Thu, Nov 30, 2017 at 11:31:47AM -0600, Aaron Sawdey wrote:
> This does some cleanup/consolidation so that bdz/bdnz are supported by
> a single insn and splitter, and adds a new insn and splitter to support
> the conditional form of those (bdzt/bdzf/bdnzt/bdnzf).
>
> This is going to
Hi!
The bswap infrastructure uses the vuse field to make sure all the loads are
having the same gimple_vuse and also uses it in bswap_replace.
When this infrastructure is used inside of the store-merging pass, the
problem is that the old stores are being removed and new added, so
gimple_vuse of th
Something to consider... I'm not suggesting we remove at this point, it
really depends on whether or not Walter wants to continue to maintain
the bits.
Forwarded Message
Subject: RFC: remove the "tile" architecture from glibc
Date: Fri, 1 Dec 2017 16:34:09 -0500
From: Chris Met
On Fri, Dec 01, 2017 at 04:48:20PM -0500, David Malcolm wrote:
> PR c/83236 reports an issue where the C FE unhelpfully suggests the use
> of glibc's private "__ino_t" type when it fails to recognize "ino_t":
>
> $ cat > test.c < #include
> ino_t inode;
> EOF
> $ gcc -std=c89 -fsyntax-only test.c
PR c/83236 reports an issue where the C FE unhelpfully suggests the use
of glibc's private "__ino_t" type when it fails to recognize "ino_t":
$ cat > test.c <
ino_t inode;
EOF
$ gcc -std=c89 -fsyntax-only test.c
test.c:2:1: error: unknown type name 'ino_t'; did you mean '__ino_t'?
ino_t inode;
^
On Fri, 2017-12-01 at 18:46 +0100, Richard Biener wrote:
> On December 1, 2017 6:22:21 PM GMT+01:00, Will Schmidt
> wrote:
> >Hi,
> >Add support for folding of vec_msum in GIMPLE.
> >
> >This uses the DOT_PROD_EXPR gimple op, which is sensitive to type
> >mismatches:
> > error: type misma
79228 points out that C++14 defines complex literal suffixes that
conflict with the GNU suffixes. In this patch I take the approach
that in C++14 and up, if has been included we assume that
the user wants the C++14 suffixes and give a hard error if they aren't
found; otherwise we assume that the
There are a number of instruction types defined in aarch64.md which do not
have pipeline/scheduling information in thunderx2-t99.md. This patch adds
some of them. This patch includes all the missing types except the neon
ones that I hope to include in a follow-up patch.
Bootstrapped and tested w
I noticed the debugging output from local-pure-const pass is missing a
newline in a couple places, leading to this:
local analysis of main
scanning: i ={v} 0;
Volatile stmt is not const/pure
Volatile operand is not const/pure scanning: j ={v} 20;
Volatile stmt is not const/pure
Hello world,
I have committed the fix for the second part (and original
test case) of PR 83224 as obvious after regression-testing
as r255331.
Regards
Thomas
2017-12-01 Thomas Koenig
PR fortran/83224
* frontend-passes.c (create_var): Also handle
character ar
On 12/01/2017 01:26 AM, Jeff Law wrote:
On 11/30/2017 01:30 PM, Martin Sebor wrote:
On 11/22/2017 05:03 PM, Jeff Law wrote:
On 11/21/2017 12:07 PM, Martin Sebor wrote:
On 11/21/2017 09:55 AM, Jeff Law wrote:
On 11/19/2017 04:28 PM, Martin Sebor wrote:
On 11/18/2017 12:53 AM, Jeff Law wrote:
On December 1, 2017 6:22:21 PM GMT+01:00, Will Schmidt
wrote:
>Hi,
>Add support for folding of vec_msum in GIMPLE.
>
>This uses the DOT_PROD_EXPR gimple op, which is sensitive to type
>mismatches:
> error: type mismatch in dot product reduction
> __vector signed int
> __vect
HI Quing,
this is a very straightforward fix for an undefined behavior in
fortran/decl.c:
> - sprintf (name, "%s_%d", name, kind_value);
> + sprintf (name + strlen (name), "_%d", kind_value);
OK for trunk. Thanks for the patch!
Regards
Thomas
Hi,
Add support for folding of vec_msum in GIMPLE.
This uses the DOT_PROD_EXPR gimple op, which is sensitive to type mismatches:
error: type mismatch in dot product reduction
__vector signed int
__vector signed char
__vector unsigned char
D.2798 = DOT_PR
It turned out that I couldn't stop and so fixed a number of other
bugs. All are minor tweaks, well hidden behind the pdt attributes.
Committed as r255311.
Paul
2017-12-01 Paul Thomas
PR fortran/82605
* resolve.c (get_pdt_constructor): Initialize 'cons' to NULL.
(resolve_pdt): Cor
Hi,
On 01/12/2017 16:43, Jeff Law wrote:
On 12/01/2017 03:28 AM, Paolo Carlini wrote:
Hi,
On 16/11/2017 16:33, Koval, Julia wrote:
// I failed to send patch itself, it is too big even in gzipped form.
What is the right way to send such big patches?
Hi, this patch removes cilkplus. Ok for tru
On 01/12/17 15:11 +, Jonathan Wakely wrote:
This fixes a number of warnings that show up with -Wsystem-headers
This fixes some more.
Tested powerpc64le-linux, committed to trunk.
commit cea830828177721a6d201dd6c201c34235626641
Author: Jonathan Wakely
Date: Fri Dec 1 15:59:01 2017 +000
On Thu, Nov 30, 2017 at 05:27:47PM +, Wilco Dijkstra wrote:
> Fix address printing for ILP32. The md file uses 'a' in assembler
> templates for symbolic addresses in adrp/add, which end up calling
> aarch64_print_operand_address. However in ILP32 these are not valid
> memory addresses (being
On 30 November 2017 at 15:56, Kyrill Tkachov
wrote:
>
> So is it the case that you don't run any arm tests that include arm_neon.h
> in your configuration?
No, it is only the case that any arm test which includes arm_neon.h
(in fact, any system header) *and* uses dg-add-options
-mfloat-abi=hard
On 12/01/2017 03:28 AM, Paolo Carlini wrote:
> Hi,
>
> On 16/11/2017 16:33, Koval, Julia wrote:
>> // I failed to send patch itself, it is too big even in gzipped form.
>> What is the right way to send such big patches?
>>
>> Hi, this patch removes cilkplus. Ok for trunk?
> Now that cilkplus is g
Certain lengths used in an MVC instruction might disable operand
forwarding. Split MVCs into up to 2 forwardable ones if possible.
Bootstrapped and regtested on s390x.
gcc/ChangeLog:
2017-12-01 Andreas Krebbel
* config/s390/predicates.md (plus16_Q_operand): New predicate.
*
On 14/11/17 13:56 -0500, Jason Merrill wrote:
While working on an unrelated issue I noticed that the compiler didn't
like some of these declarations after preprocessing, when they aren't
protected by system-header permissiveness.
I thought about limiting the permissiveness to only extern "C"
fun
This fixes a number of warnings that show up with -Wsystem-headers
Tested powerpc64le-linux, committed to trunk.
commit cc833c247c3b334c56feff8898bd02c8f9f3fc6a
Author: Jonathan Wakely
Date: Fri Dec 1 14:13:47 2017 +
Add comment to fix -Wfallthrough warning
* includ
On 01/12/17 14:34 +, Jonathan Wakely wrote:
On 01/12/17 15:22 +0100, Paolo Carlini wrote:
Hi,
On 01/12/2017 15:11, Jonathan Wakely wrote:
On 01/12/17 14:02 +, Jonathan Wakely wrote:
Is there a reason we left-shift into the sign bit, causing undefined
behaviour? The approach used in st
C++14 added noexcept to the integral_constant member functions, and it
should always have been on the integer_sequence one.
* include/std/type_traits (integral_constant): Make member functions
noexcept (LWG 2346).
* include/std/utility (integer_sequence): Likewise.
Tested
Hi,
this is a very straightforward fix for an undefined behavior in fortran/decl.c:
In the man page of sprintf, it's clearly state:
===
NOTES
Some programs imprudently rely on code such as the following
sprintf(buf, "%s some further text", buf);
to append text to buf. H
On Fri, Dec 1, 2017 at 2:26 PM, Richard Biener wrote:
> On Fri, 1 Dec 2017, Bin.Cheng wrote:
>
>> On Fri, Dec 1, 2017 at 12:31 PM, Richard Biener wrote:
>> >
>> > This is the access stride computation change. Apart from the
>> > stride extraction I adjusted the cost model to handle non-constant
On Fri, Dec 01, 2017 at 03:41:49PM +0100, Jan Hubicka wrote:
> @@ -99,25 +97,25 @@ DEF_TUNE (X86_TUNE_MEMORY_MISMATCH_STALL
> conditional jump instruction for 32 bit TARGET.
> FIXME: revisit for generic. */
Remove the last line of the comment above?
> DEF_TUNE (X86_TUNE_FUSE_CMP_AND_BRA
Hi,
this patch updates tuning flags for generic. It drops flags used by old
chips (X86_TUNE_PARTIAL_FLAG_REG_STALL which is needed only for original
core2, X86_TUNE_PAD_RETURNS which is needed for pre-buldozer chips)
and enables fussion logic because it seems wasteful to let scheduler
prevent it.
This patch fixes a race condition bug in
libgomp.oacc-c-c++-common/data-2-lib.c. That is an OpenACC test which
exercises the runtime wait API, for use in conjunction with asynchronous
OpenACC offloaded regions. I not sure why this problem went undetected
for so long. Either the parallel region runs
On 01/12/17 15:22 +0100, Paolo Carlini wrote:
Hi,
On 01/12/2017 15:11, Jonathan Wakely wrote:
On 01/12/17 14:02 +, Jonathan Wakely wrote:
Is there a reason we left-shift into the sign bit, causing undefined
behaviour? The approach used in std::numeric_limits seems better.
The current cod
On Fri, 1 Dec 2017, Bin.Cheng wrote:
> On Fri, Dec 1, 2017 at 12:31 PM, Richard Biener wrote:
> >
> > This is the access stride computation change. Apart from the
> > stride extraction I adjusted the cost model to handle non-constant
> > strides by checking if either is a multiple of the other a
Hi,
On 01/12/2017 15:11, Jonathan Wakely wrote:
On 01/12/17 14:02 +, Jonathan Wakely wrote:
Is there a reason we left-shift into the sign bit, causing undefined
behaviour? The approach used in std::numeric_limits seems better.
The current code warns with -Wpedantic -Wsystem-headers:
/usr
On 01/12/17 14:02 +, Jonathan Wakely wrote:
Is there a reason we left-shift into the sign bit, causing undefined
behaviour? The approach used in std::numeric_limits seems better.
The current code warns with -Wpedantic -Wsystem-headers:
/usr/include/c++/7/ext/numeric_traits.h:58:35: warning
Is there a reason we left-shift into the sign bit, causing undefined
behaviour? The approach used in std::numeric_limits seems better.
commit e18203057f8e46a3b35239977d8d703df47cdc28
Author: Jonathan Wakely
Date: Thu Nov 30 18:15:49 2017 +
Fix overflow
diff --git a/libstdc++-v3/incl
On Fri, Dec 01, 2017 at 01:18:43PM +0100, Jakub Jelinek wrote:
> > Furthermore this
> >
> > typedef double __attribute__((vector_size(16))) v2df_t;
> > typedef double __attribute__((vector_size(32))) v4df_t;
> >
> > void test1(void) {
> > register v2df_t x asm("xmm31") = {};
> > asm volat
On Fri, Dec 1, 2017 at 12:31 PM, Richard Biener wrote:
>
> This is the access stride computation change. Apart from the
> stride extraction I adjusted the cost model to handle non-constant
> strides by checking if either is a multiple of the other and
> simply fail interchanging if it's the wrong
Hi,
this version of the patch improves the heuristic check to take the
target hook into account, to handle cases correctly when both or only
one parameter is _not_ promoted to int.
Both C and C++ FE should of course use the same logic here.
Bootstrapped and reg-tested on x86_64-pc-linux-gnu.
Is
This is the access stride computation change. Apart from the
stride extraction I adjusted the cost model to handle non-constant
strides by checking if either is a multiple of the other and
simply fail interchanging if it's the wrong way around for one
ref or if the simple method using multiple_of
Tested on x86_64-unknown-linux-gnu, applied.
Richard.
2017-12-01 Richard Biener
* gfortran.dg/pr81303.f: New testcase.
Index: gcc/testsuite/gfortran.dg/pr81303.f
===
--- gcc/testsuite/gfortran.dg/pr81303.f (nonexistent)
On Fri, Dec 1, 2017 at 11:53 AM, Bin Cheng wrote:
> Hi,
> This is a simple patch using dyn_cast instead of is_a<> and as_a<> as
> suggested by review.
> This is for branches/gimple-linterchange, bootstrap and test as when the
> branch is created. Is it OK?
Ok.
Richard.
> Thanks,
> bin
> 20
On Thu, Nov 30, 2017 at 2:18 PM, Richard Sandiford
wrote:
> Richard Sandiford writes:
>> Richard Biener writes:
>>> On Wed, Nov 29, 2017 at 12:57 PM, Richard Sandiford
>>> wrote:
It was clear from the SVE reviews that people were unhappy with how
"special" the variable-length case was
The following fixes an old missed basic-block vectorization issue
exposing itself as regression caused by a x86 cost change lumping a
lot more code into the same BB.
We are sorting DRs after constant offset and if there are multiple
refs with the same offset we break the DR group. This doesn't h
Hi,
This is a simple patch using dyn_cast instead of is_a<> and as_a<> as suggested
by review.
This is for branches/gimple-linterchange, bootstrap and test as when the branch
is created. Is it OK?
Thanks,
bin
2017-11-30 Bin Cheng
* gimple-loop-interchange.cc (is-a.h): New header fil
Hi,
On 16/11/2017 16:33, Koval, Julia wrote:
// I failed to send patch itself, it is too big even in gzipped form. What is
the right way to send such big patches?
Hi, this patch removes cilkplus. Ok for trunk?
Now that cilkplus is gone I suppose we should clean-up Bugzilla about
that. Shall
On 30/11/17 16:07, Kyrill Tkachov wrote:
On 30/11/17 16:06, Sudakshina Das wrote:
Hi Kyrill
On 27/11/17 12:25, Kyrill Tkachov wrote:
> Hi Sudi,
>
> On 24/11/17 14:57, Sudi Das wrote:
>> Hi
>>
>> For the following test case:
>> __fp16
>> test_select (__fp16 a, __fp16 b, __fp16 c)
>> {
>>ret
Ping,
This patch has also been bootstrapped and no issues.
> -Original Message-
> From: Tamar Christina
> Sent: Tuesday, November 21, 2017 17:29
> To: Tamar Christina ; gcc-patches@gcc.gnu.org
> Cc: nd ; Ramana Radhakrishnan
> ; Richard Earnshaw
> ; ni...@redhat.com; Kyrylo Tkachov
>
>
On 11/30/2017 01:30 PM, Martin Sebor wrote:
> On 11/22/2017 05:03 PM, Jeff Law wrote:
>> On 11/21/2017 12:07 PM, Martin Sebor wrote:
>>> On 11/21/2017 09:55 AM, Jeff Law wrote:
On 11/19/2017 04:28 PM, Martin Sebor wrote:
> On 11/18/2017 12:53 AM, Jeff Law wrote:
>> On 11/17/2017 12:36
72 matches
Mail list logo
