On Thu, Nov 17, 2016 at 9:41 AM, Thomas Koenig wrote:
> Am 17.11.2016 um 00:20 schrieb Jakub Jelinek:
>>
>> On Thu, Nov 17, 2016 at 12:03:18AM +0100, Thomas Koenig wrote:
Don't you need to test in configure if the assembler supports AVX?
Otherwise if somebody
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66227
--- Comment #7 from janus at gcc dot gnu.org ---
Author: janus
Date: Thu Nov 17 07:52:24 2016
New Revision: 242535
URL: https://gcc.gnu.org/viewcvs?rev=242535=gcc=rev
Log:
2016-11-17 Janus Weil
PR fortran/66227
Am 17.11.2016 um 00:20 schrieb Jakub Jelinek:
On Thu, Nov 17, 2016 at 12:03:18AM +0100, Thomas Koenig wrote:
Don't you need to test in configure if the assembler supports AVX?
Otherwise if somebody is bootstrapping gcc with older assembler, it will
just fail to bootstrap.
That's a good point.
On 17 November 2016 at 03:20, Jeff Law wrote:
> On 11/16/2016 01:23 PM, Prathamesh Kulkarni wrote:
>>
>> Hi,
>> As discussed in PR, this patch marks the test-case to xfail on
>> arm-none-eabi.
>> OK to commit ?
>
> You might check if Aldy's change to the uninit code helps your
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78386
--- Comment #5 from Andrew Pinski ---
Does -ffp-contract=off help?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78387
Thomas Koenig changed:
What|Removed |Added
Status|RESOLVED|NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78357
--- Comment #11 from Sebastian Huber ---
Thanks for your kind help. Would it be possible to back port this to GCC 6
also?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78357
--- Comment #10 from Chung-Lin Tang ---
Author: cltang
Date: Thu Nov 17 06:26:56 2016
New Revision: 242534
URL: https://gcc.gnu.org/viewcvs?rev=242534=gcc=rev
Log:
2016-11-17 Chung-Lin Tang
PR target/78357
On 11/16/2016 05:17 PM, Martin Sebor wrote:
(I've heard some noise in C++-land about making memcpy(0,0,0) valid, but
that may have just been noise)
We may have read the same discussion. It would make some things
a little easier in C++ (and remove what most people view as yet
another
> GCC is built with -fno-exceptions. I assume that's mainly to avoid
> having to catch and handle exceptions in what was originally C code.
> I also assume that also means that there's a policy or convention in
> place against throwing exceptions in GCC or making use of constructs
> that might
On 11/16/2016 07:36 PM, Segher Boessenkool wrote:
On Wed, Nov 16, 2016 at 01:48:41PM -0700, Martin Sebor wrote:
I'm also curious if there really is a policy/convention for dealing
with exceptions in GCC, what it actually is/says.
https://gcc.gnu.org/codingconventions.html#Exceptions
Thanks.
On 11/16/16 9:08 AM, Richard Biener wrote:
> On Tue, Nov 15, 2016 at 9:03 PM, Bill Schmidt
> wrote:
>> - if ((any_pred_load_store || any_complicated_phi)
>> - && !version_loop_for_if_conversion (loop))
>> + /* Since we have no cost model, always version loops
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78304
--- Comment #2 from Marek Polacek ---
Even though that with my patch we expansion_point_location_if_in_system_header
the caret location, it still points to the location in the system header, so
the diagnostics is suppressed.
ping...
On Thu, Nov 3, 2016 at 7:58 PM, Paul Hua wrote:
> Hi Matthew,
>
> Thanks for your comments, update the patch.
>
> *** gcc/ChangeLog ***
>
> 2016-11-03 Chenghua Xu
>
> * config/mips/mips.h (ISA_HAS_FUSED_MADD4): Enable for
>
On Wed, Nov 16, 2016 at 01:48:41PM -0700, Martin Sebor wrote:
> I'm also curious if there really is a policy/convention for dealing
> with exceptions in GCC, what it actually is/says.
https://gcc.gnu.org/codingconventions.html#Exceptions
Segher
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78351
--- Comment #20 from Steve Kargl ---
On Thu, Nov 17, 2016 at 01:44:45AM +, sgk at troutmask dot
apl.washington.edu wrote:
>
> In the above, you are hitting an end-of-record. I would need
> to go read the Standard to see what happens in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78304
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78351
--- Comment #19 from Steve Kargl ---
On Thu, Nov 17, 2016 at 12:43:40AM +, kevin.b.beard at nasa dot gov wrote:
> Many thanks to Jerry DeLisle [jvdeli...@charter.net]; he made us realize
> that an internal record is now not treated the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78285
Marek Polacek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78285
--- Comment #2 from Marek Polacek ---
Author: mpolacek
Date: Thu Nov 17 01:23:19 2016
New Revision: 242532
URL: https://gcc.gnu.org/viewcvs?rev=242532=gcc=rev
Log:
PR c/78285
* c-common.c (c_add_case_label): Turn error_at calls
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78387
--- Comment #5 from Andrew Benson ---
I couldn't find anything in the OpenMP specifications which addresses this
issue - so presumably it's undefined behavior as far as OpenMP is concerned.
But it seems that internal file writes were intended to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390
Bug ID: 78390
Summary: Bootstrap failure: match.pd: cannot determine type of
operand
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
On Wed, 16 Nov 2016, Marek Polacek wrote:
> As pointed out in Bug 78285, some error calls should actually be inform calls.
> I'm not adding any new test; existing switch-5.c covers all the cases so I
> didn't
> see much value in duplicating that part of the test.
>
> Bootstrapped/regtested on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78252
Nathan Sidwell changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78252
--- Comment #2 from Nathan Sidwell ---
Created attachment 40062
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40062=edit
reduced source code
I've reduced the original source to the attached. This emits 4 function
symbols, 2 of which are
I'll presume you know best about the choices of stdint.h types. You may
wish to consider what the correct value of use_gcc_stdint is - the
default "none" (rely on the system's header), or "wrap" (use GCC's header
in freestanding mode) or "provide" (always use GCC's header).
Note that GCC's
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58001
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|WAITING |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78351
--- Comment #17 from Dr. Kevin B. Beard ---
Hi,
Many thanks to Jerry DeLisle [jvdeli...@charter.net]; he made us realize
that an internal record is now not treated the same as an external record! I
didn't think of that.
In the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78351
--- Comment #18 from Dr. Kevin B. Beard ---
Created attachment 40061
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40061=edit
x2.dat
On 11/16/2016 05:17 PM, Martin Sebor wrote:
On 11/16/2016 02:21 PM, Marc Glisse wrote:
On Wed, 16 Nov 2016, Martin Sebor wrote:
On 11/16/2016 11:49 AM, Prathamesh Kulkarni wrote:
Hi Richard,
Following your suggestion in PR78154, the patch checks if stmt
contains call to memmove (and friends)
On Fri, Nov 04, 2016 at 05:16:00PM +0100, Jakub Jelinek wrote:
> On Fri, Nov 04, 2016 at 05:05:51PM +0100, Marek Polacek wrote:
> > This is a similar case to PR sanitizer/70342. Here, we were generating
> > expression
> > in a quadratic fashion because of the initializer--we create SAVE_EXPR <>,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58001
--- Comment #14 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Thu Nov 17 00:18:18 2016
New Revision: 242530
URL: https://gcc.gnu.org/viewcvs?rev=242530=gcc=rev
Log:
2016-11-16 Steven G. Kargl
PR
On 11/16/2016 02:21 PM, Marc Glisse wrote:
On Wed, 16 Nov 2016, Martin Sebor wrote:
On 11/16/2016 11:49 AM, Prathamesh Kulkarni wrote:
Hi Richard,
Following your suggestion in PR78154, the patch checks if stmt
contains call to memmove (and friends) in gimple_stmt_nonzero_warnv_p
and returns
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70548
Henrique Andrade changed:
What|Removed |Added
CC||hcma at unscrambl dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78387
Jerry DeLisle changed:
What|Removed |Added
CC||jvdelisle at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78355
--- Comment #7 from pipcet at gmail dot com ---
(In reply to Eric Botcazou from comment #6)
> > The analysis looks right for me. Although this code had a lot of troubles
> > until it was stabilized and came to the current state. So the change
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78386
--- Comment #4 from joseph at codesourcery dot com ---
On Wed, 16 Nov 2016, pinskia at gcc dot gnu.org wrote:
> Most likely the use of fma.
Which applies with current x86_64 just as it does with powerpc. It should
be possible to reduce such
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78373
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78378
Jakub Jelinek changed:
What|Removed |Added
Summary|[5/6/7 Regression] wrong|[5/6 Regression] wrong code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78378
--- Comment #7 from Jakub Jelinek ---
Author: jakub
Date: Wed Nov 16 23:22:16 2016
New Revision: 242526
URL: https://gcc.gnu.org/viewcvs?rev=242526=gcc=rev
Log:
PR rtl-optimization/78378
* combine.c (make_extraction): Use
On Thu, Nov 17, 2016 at 12:03:18AM +0100, Thomas Koenig wrote:
> >Don't you need to test in configure if the assembler supports AVX?
> >Otherwise if somebody is bootstrapping gcc with older assembler, it will
> >just fail to bootstrap.
>
> That's a good point. The AVX instructions were added in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78325
Alan Modra changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
On Wed, Nov 16, 2016 at 02:56:03PM -0800, Ian Lance Taylor wrote:
> On Wed, Nov 16, 2016 at 2:18 PM, David Tolnay wrote:
> > FSF just confirmed that my assignment/disclaimer process has been
> > completed. Ian can you take a look at your list again?
>
> Yes, you are good.
On Wed, Nov 16, 2016 at 10:07:23PM +0100, Jakub Jelinek wrote:
> If inner is a MEM, make_extraction requires that pos is a multiple of bytes
> and deals with offsetting it. Or otherwise requires that pos is a multiple
> of BITS_PER_WORD and for REG inner it handles that too. But if inner
> is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70890
--- Comment #10 from Alan Modra ---
Author: amodra
Date: Wed Nov 16 23:10:55 2016
New Revision: 242525
URL: https://gcc.gnu.org/viewcvs?rev=242525=gcc=rev
Log:
R_MIPS_JALR failures
This is a fix for my PR70890 patch, which incorrectly removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78325
--- Comment #4 from Alan Modra ---
Author: amodra
Date: Wed Nov 16 23:10:55 2016
New Revision: 242525
URL: https://gcc.gnu.org/viewcvs?rev=242525=gcc=rev
Log:
R_MIPS_JALR failures
This is a fix for my PR70890 patch, which incorrectly removed
On 11/16/2016 01:30 PM, Thomas Koenig wrote:
Hello world,
the attached patch adds an AVX-specific version of the matmul
intrinsic to the Fortran library. This works by using the target_clones
attribute.
For testing, I compiled this on powerpc64-unknown-linux-gnu,
without any ill effects.
Am 16.11.2016 um 23:01 schrieb Jakub Jelinek:
On Wed, Nov 16, 2016 at 10:30:03PM +0100, Thomas Koenig wrote:
the attached patch adds an AVX-specific version of the matmul
intrinsic to the Fortran library. This works by using the target_clones
attribute.
Don't you need to test in configure if
On Wed, Nov 16, 2016 at 2:18 PM, David Tolnay wrote:
> FSF just confirmed that my assignment/disclaimer process has been
> completed. Ian can you take a look at your list again?
Yes, you are good. Thanks.
Ian
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78373
--- Comment #4 from Jason Merrill ---
Author: jason
Date: Wed Nov 16 22:42:24 2016
New Revision: 242523
URL: https://gcc.gnu.org/viewcvs?rev=242523=gcc=rev
Log:
PR c++/78373 - ICE with TREE_CONSTANT reference
* decl.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78389
Bug ID: 78389
Summary: list::merge and list::sort are not exception safe
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
On Wed, Nov 16, 2016 at 1:45 PM, Moore, Catherine
wrote:
> /scratch/cmoore/mips-sde-elf-upstream/src/gcc-trunk-6/gcc/hash-map.h:62:12:
> error: no matching function for call to 'gt_ggc_mx(rtx_def*&)'
>
> I configured with --target=mips-sde-elf, but I do have some
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77848
--- Comment #24 from Bill Schmidt ---
The above commit doesn't yet solve the problem, but enables more outer-loop
vectorization in preparation for the fix.
FSF just confirmed that my assignment/disclaimer process has been
completed. Ian can you take a look at your list again?
David
On Fri, Nov 11, 2016 at 1:48 PM, David Tolnay wrote:
> On Fri, Nov 11, 2016 at 10:46 AM, Ian Lance Taylor wrote:
>> The patch is OK
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77848
--- Comment #23 from Bill Schmidt ---
Author: wschmidt
Date: Wed Nov 16 22:17:10 2016
New Revision: 242520
URL: https://gcc.gnu.org/viewcvs?rev=242520=gcc=rev
Log:
2016-11-16 Bill Schmidt
PR
* Mike Stump [2016-11-16 12:59:53 -0800]:
> On Nov 16, 2016, at 12:09 PM, Andrew Burgess
> wrote:
> > My only remaining concern is the new tests, I've tried to restrict
> > them to targets that I suspect they'll pass on with:
> >
> >/* {
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66742
--- Comment #9 from TC ---
The ugly fix in Comment #6 should be performant, if, well, ugly.
It may be worth considering holding the nodes via a different type. There's no
real reason why the temporary holders need to be a `list` or have a copy
As pointed out in Bug 78285, some error calls should actually be inform calls.
I'm not adding any new test; existing switch-5.c covers all the cases so I
didn't
see much value in duplicating that part of the test.
Bootstrapped/regtested on x86_64-linux, ok for trunk?
2016-11-16 Marek Polacek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78324
--- Comment #1 from David Malcolm ---
Root cause is that the substring loc code isn't set up to cope with
-ftrack-macro-expansion=0, and attempts to handle this location:
../../src/gcc/testsuite/gcc.dg/tree-ssa/builtin-sprintf-2.c:95:1: note:
On Wed, Nov 16, 2016 at 10:30:03PM +0100, Thomas Koenig wrote:
> the attached patch adds an AVX-specific version of the matmul
> intrinsic to the Fortran library. This works by using the target_clones
> attribute.
Don't you need to test in configure if the assembler supports AVX?
Otherwise if
Committed after approval on bugzilla to eliminate warnings.
2016-11-16 Jerry DeLisle
PR libgfortran/51119
* Makefile.am: Remove -fno-protect-parens -fstack-arrays.
* Makefile.in: Regenerate.
r242517 = 026291bdda18395d7c746856dd7e4ed384856a1b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51119
--- Comment #47 from Jerry DeLisle ---
Author: jvdelisle
Date: Wed Nov 16 21:54:25 2016
New Revision: 242518
URL: https://gcc.gnu.org/viewcvs?rev=242518=gcc=rev
Log:
2016-11-16 Jerry DeLisle
PR
On Wed, 16 Nov 2016, Matthew Fortune wrote:
> OK. I have no idea what system supports 64-bit MIPS16 but given it costs
> little to improve consistency here then it is at least doing no harm.
No recent real hardware I believe. Among older implementations there
were the NEC Vr4111 and Vr4121
On Wed, Nov 16, 2016 at 04:26:36PM -0500, Jason Merrill wrote:
> On Wed, Nov 16, 2016 at 4:00 PM, Jakub Jelinek wrote:
> > Jason's recent patch to turn reference vars initialized with invariant
> > addresses broke the first testcase below, because >singleton
> > is considered
On 11/16/2016 01:23 PM, Prathamesh Kulkarni wrote:
Hi,
As discussed in PR, this patch marks the test-case to xfail on arm-none-eabi.
OK to commit ?
You might check if Aldy's change to the uninit code helps your case
(approved earlier today, so hopefully in the tree very soon). I quickly
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78355
--- Comment #6 from Eric Botcazou ---
> The analysis looks right for me. Although this code had a lot of troubles
> until it was stabilized and came to the current state. So the change might
> create some new failures but I hope it will not.
> On Nov 16, 2016, at 11:23 AM, Krister Walfridsson
> wrote:
>
> On Wed, 16 Nov 2016, Mike Stump wrote:
>
>> Looks reasonable. The biggest issue would be if any of those values changed
>> through time, and the current version works for older netbsd releases,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58001
kargl at gcc dot gnu.org changed:
What|Removed |Added
CC||kargl at gcc dot gnu.org
---
An earlier version of the attached patch lingered in bugzilla
for over 3 years. I've updated the patch to include Manuel's
comment #12. Regression tested on x86_64-*-freebsd. OK to
commit?
2016-11-16 Steven G. Kargl
PR fortran/58001
* io.c
Hello world,
the attached patch adds an AVX-specific version of the matmul
intrinsic to the Fortran library. This works by using the target_clones
attribute.
For testing, I compiled this on powerpc64-unknown-linux-gnu,
without any ill effects.
Also, a resulting binary reached around 15 GFlops
On Tue, Nov 15, 2016 at 11:31 AM, Jason Merrill wrote:
> OK, (hopefully) one more patch for decltype and C++17 decomposition
> declarations. I hadn't been thinking that "referenced type" meant to
> look through references in the tuple case, since other parts of
> [dcl.decomp]
On Wed, Nov 16, 2016 at 4:00 PM, Jakub Jelinek wrote:
> Jason's recent patch to turn reference vars initialized with invariant
> addresses broke the first testcase below, because >singleton
> is considered TREE_CONSTANT (because self is TREE_CONSTANT VAR_DECL and
> singleton
On Wed, 16 Nov 2016, Martin Sebor wrote:
On 11/16/2016 11:49 AM, Prathamesh Kulkarni wrote:
Hi Richard,
Following your suggestion in PR78154, the patch checks if stmt
contains call to memmove (and friends) in gimple_stmt_nonzero_warnv_p
and returns true in that case.
Nice. I think the list
On 15 November 2016 at 12:50, Jonathan Wakely wrote:
> On 14/11/16 14:32 +0100, Christophe Lyon wrote:
>>
>> On 20 October 2016 at 19:40, Jonathan Wakely wrote:
>>>
>>> On 20/10/16 10:33 -0700, Mike Stump wrote:
On Oct 20, 2016, at 9:34 AM,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78388
Bug ID: 78388
Summary: Bogus "declaration shadows template parameter" error
with parenthesized function-style casts
Product: gcc
Version: 7.0
Status: UNCONFIRMED
On Wed, 16 Nov 2016, Matthew Fortune wrote:
> > Fix `-mrelax-pic-calls' support for microMIPS code where the relocation
> > produced is supposed to be R_MICROMIPS_JALR rather than R_MIPS_JALR.
> > The lack of short delay support comes from a missed update to this code
> > for microMIPS support
Hi!
If inner is a MEM, make_extraction requires that pos is a multiple of bytes
and deals with offsetting it. Or otherwise requires that pos is a multiple
of BITS_PER_WORD and for REG inner it handles that too. But if inner
is something different, it calls just force_to_mode to the target mode,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78386
Bill Schmidt changed:
What|Removed |Added
Target||powerpc64le-unknown-linux-g
On 11/02/2016 11:16 AM, Aldy Hernandez wrote:
Hi Jeff.
As discussed in the PR, here is a patch exploring your idea of ignoring
unguarded uses if we can prove that the guards for such uses are
invalidated by the uninitialized operand paths being executed.
This is an updated patch from my
Hi!
Jason's recent patch to turn reference vars initialized with invariant
addresses broke the first testcase below, because >singleton
is considered TREE_CONSTANT (because self is TREE_CONSTANT VAR_DECL and
singleton field has constant offset), but after going into SSA form
it is not supposed to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68778
janus at gcc dot gnu.org changed:
What|Removed |Added
Keywords||wrong-code
On Nov 16, 2016, at 12:09 PM, Andrew Burgess
wrote:
> My only remaining concern is the new tests, I've tried to restrict
> them to targets that I suspect they'll pass on with:
>
>/* { dg-final-use { scan-assembler "\.section\[\t
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78285
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78383
--- Comment #2 from Marek Polacek ---
I mean r160122 or r160124.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78386
--- Comment #2 from Breno Leitao ---
I did further tests with older versions, and the problem is also reproducible,
so, this is not a regression.
These are the versions I tested also:
* gcc-5 (Debian 5.4.1-3) 5.4.1 20161019
* gcc-4 (Debian
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68377
Markus Trippelsdorf changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
---
GCC is built with -fno-exceptions. I assume that's mainly to avoid
having to catch and handle exceptions in what was originally C code.
I also assume that also means that there's a policy or convention in
place against throwing exceptions in GCC or making use of constructs
that might throw (such
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78387
--- Comment #3 from Jakub Jelinek ---
I thought they are supposed to be, at least that is what we had unit_lock,
u->lock etc. for. So has something in libgfortran changed so that it doesn't
properly lock the units anymore?
On Tue, Nov 15, 2016 at 10:50 PM, Andrew Senkevich
wrote:
> Hi,
>
> this is follow-up with tests for new __target__ attributes and
> __builtin_cpu_supports update.
>
> gcc/
> * config/i386/i386.c (processor_features): Add
> F_AVX5124VNNIW,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78383
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78387
--- Comment #2 from Andrew Benson ---
OK - thanks. I hadn't realized that the internal I/O operations weren't
threadsafe - I guess I've just been fortunate to avoid this with previous
versions of gfortran. I'll update my code to use critical
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78387
Thomas Koenig changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
On Wed, Nov 16, 2016 at 12:50 PM, Jason Merrill wrote:
> On Fri, Nov 11, 2016 at 1:33 PM, Jiong Wang wrote:
>> The encoding for new added AARCH64 DWARF operations.
>
> This patch seems rather incomplete; I only see a change to
> dwarf2out.c, which won't
On 11/16/2016 11:49 AM, Prathamesh Kulkarni wrote:
Hi Richard,
Following your suggestion in PR78154, the patch checks if stmt
contains call to memmove (and friends) in gimple_stmt_nonzero_warnv_p
and returns true in that case.
Nice. I think the list should also include mempcpy, stpcpy, and
us/Tools/libexec/gcc/x86_64-pc-linux-gnu/7.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc-trunk/configure --prefix=/home/abenson/Galacticus/Tools
--enable-languages=c,c++,fortran --disable-multilib
Thread model: posix
gcc version 7.0.0 20161116 (experimental) (GCC)
$ gfortran t
Hi,
As discussed in PR, this patch marks the test-case to xfail on arm-none-eabi.
OK to commit ?
Thanks,
Prathamesh
2016-11-17 Prathamesh Kulkarni
PR tree-optimization/78319
testsuite/
* gcc.dg/uninit-pred-8_a.c (foo): Mark dg-bogus test to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72823
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78386
--- Comment #1 from Andrew Pinski ---
Most likely the use of fma.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78386
Bug ID: 78386
Summary: Powerpc64le: optimization -O2 and higher cause math
inconsitency
Product: gcc
Version: 6.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72823
--- Comment #9 from Jakub Jelinek ---
Author: jakub
Date: Wed Nov 16 20:10:27 2016
New Revision: 242510
URL: https://gcc.gnu.org/viewcvs?rev=242510=gcc=rev
Log:
PR bootstrap/72823
* configure.ac (ENABLE_ASSERT_CHECKING): Define
1 - 100 of 599 matches
Mail list logo