https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82598
Bug ID: 82598
Summary: lto debugobj lacks .note.GNU-stack
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: lto
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81797
Campbell changed:
What|Removed |Added
CC||rlcamp.pdx at gmail dot com
--- Comment #21
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82597
Bug ID: 82597
Summary: ICE at -O2 and -O3 x86_64-linux-gnu in the 32-bit
mode: in extract_constrain_insn, at recog.c:2207
Product: gcc
Version: unknown
Status:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82588
Martin Sebor changed:
What|Removed |Added
Keywords||patch
--- Comment #3 from Martin Sebor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82596
Martin Sebor changed:
What|Removed |Added
Keywords||patch
--- Comment #2 from Martin Sebor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82583
Martin Sebor changed:
What|Removed |Added
Keywords||patch
--- Comment #2 from Martin Sebor
While testing my latest -Wrestrict changes I noticed a number of
opportunities to improve the -Warray-bounds warning. Attached
is a patch that implements a solution for the following subset
of these:
PR tree-optimization/82596 - missing -Warray-bounds on an out-of
bounds index into string
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82556
--- Comment #6 from Vladimir Makarov ---
(In reply to Jakub Jelinek from comment #5)
> Indeed started with my r253710. If there is something wrong on the
> constraints on the patterns, please let me know.
The constraints are ok. I'll probably
On 10/17/2017 03:55 PM, Manuel López-Ibáñez wrote:
On 13/10/17 02:47, Martin Sebor wrote:
[*] We wrote a script scrape those off the online HTML manual
and create a "database" mapping options to GCC versions they
were introduced in (or first documented in, as not every option
always gets
On 10/17/2017 11:33 AM, David Malcolm wrote:
This patch depends on:
* "[PATCH] c-family: add name_hint/deferred_diagnostic (v2)"
* https://gcc.gnu.org/ml/gcc-patches/2017-10/msg01021.html
(waiting review)
* [PATCH 3/3] C: hints for missing stdlib includes for macros and types
*
On Tue, Oct 17, 2017 at 06:14:16PM -0700, Jerry DeLisle wrote:
> On 10/17/2017 03:36 PM, Thomas Koenig wrote:
> > Hello world,
> >
> > this patch fixes a regression with long compile times,
> > which came about due to our handling of array constructors
> > at compile time. This, togeteher with a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82582
--- Comment #1 from Andrew Pinski ---
For AARCH64 the correct thing is able to be produced:
foo32:
sub w2, w2, w2, lsl 2 ; w2 = z - z<<2; (rather -z*3)
neg w0, w0, lsl 1 ; w0 = x * -2
maddw0, w0, w1, w2
On 10/12/2017 03:19 PM, Tsimbalist, Igor V wrote:
> Enable building libobjc with Intel CET options.
>
> libobjc/
> * Makefile.in: Regenerate.
> * aclocal.m4: Likeiwse.
> * configure: Likewise.
> * configure.ac: Set CET_FLAGS. Update XCFLAGS.
>
Same comments as the
On 10/12/2017 02:34 PM, Tsimbalist, Igor V wrote:
> Enable building libquadmath with Intel CET options.
>
> libquadmath/
> * Makefile.am: Update AM_CFLAGS.
> * Makefile.in: Regenerate:
> * acinclude.m4: Add enable.m4 and cet.m4.
> * configure: Regenerate.
> *
On 10/12/2017 02:36 PM, Tsimbalist, Igor V wrote:
> Enable building libmpx with Intel CET options.
>
> libmpx/
> * Makefile.in: Regenerate.
> * acinclude.m4: Add enable.m4 and cet.m4.
> * configure: Regenerate.
> * configure.ac: Set CET_FLAGS. Update XCFLAGS.
> *
On 10/12/2017 02:31 PM, Tsimbalist, Igor V wrote:
> Enable building libssp with Intel CET options.
>
> libssp/
> * Makefile.am: Update AM_CFLAGS.
> * Makefile.in: Regenerate.
> * configure: Likewise.
> * aclocal.m4: Likewise.
> * configure.ac: Set CET_FLAGS. Update
On 10/12/2017 02:29 PM, Tsimbalist, Igor V wrote:
> Enable building libvtv with Intel CET options.
>
> libvtv/
> * acinclude.m4: Add enable.m4 and cet.m4.
> * libvtv/configure: Regenerate.
> * libvtv/configure.ac: Set CET_FLAGS. Update XCFLAGS.
Same comments as with libcilkrts.
On 10/12/2017 03:17 PM, Tsimbalist, Igor V wrote:
> Enable building libgfortran with Intel CET options.
>
> libgfortran/
> * acinclude.m4: Add enable.m4, cet.m4.
> * configure: Regenerate.
> * configure.ac: Set CET_FLAGS. Update AM_FCFLAGS, AM_CFLAGS,
> CFLAGS.
>
Same
On 10/12/2017 02:27 PM, Tsimbalist, Igor V wrote:
> Enable building libsanitizer with Intel CET options.
>
> libsanitizer/
> * acinclude.m4: Add enable.m4 and cet.m4.
> * Makefile.in: Regenerate.
> * asan/Makefile.am: Update AM_CXXFLAGS.
> * asan/Makefile.in: Regenerate.
>
On 10/12/2017 02:18 PM, Tsimbalist, Igor V wrote:
> Enable building libatomic with CET options.
>
> libatomic/
> * configure.ac: Set CET_FLAGS, update XCFLAGS.
> * acinclude.m4: Add cet.m4 and enable.m4.
> * configure: Regenerate.
> * Makefile.in: Likewise.
> *
On 10/12/2017 02:20 PM, Tsimbalist, Igor V wrote:
> Enable building libgomp with CET options.
>
> libgomp/
> * configure.ac: Set CET_FLAGS, update XCFLAGS and FCFLAGS.
> * acinclude.m4: Add cet.m4.
> * configure: Regenerate.
> * Makefile.in: Likewise.
> *
On 10/12/2017 02:13 PM, Tsimbalist, Igor V wrote:
> Enable building libcilkrts with CET options.
>
> libcilkrts/
> * Makefile.am: Add AM_CXXFLAGS and XCXXFLAGS.
> * configure.ac: Set CET_FLAGS, update XCFLAGS, XCXXFLAGS.
> * Makefile.in: Regenerate.
> * aclocal.m4:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82596
Martin Sebor changed:
What|Removed |Added
Keywords||diagnostic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82583
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82588
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82596
Bug ID: 82596
Summary: missing -Warray-bounds on an out-of-bounds index into
string literal
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
On 10/17/2017 03:36 PM, Thomas Koenig wrote:
> Hello world,
>
> this patch fixes a regression with long compile times,
> which came about due to our handling of array constructors
> at compile time. This, togeteher with a simplification in
> front end optimization, led to long compile times and
On 10/15/2017 11:09 AM, Thomas Koenig wrote:
> Hello world,
>
> the attached patch fixes a regression by turning an ICE-on-invalid into
> an error message (and making sure that it fits).
>
> Regression-tested on trunk.
>
> OK for all affected branches (8/7/6)?
>
Yes, OK, thanks.
Jerry
On 10/17/2017 11:33 AM, Paul Richard Thomas wrote:
> The attached patch has a comment that explains what is going on.
>
> Bootstrapped and regtested on FC23/x86_64 - OK for trunk and 7-branch?
>
Yes, looks OK for both. Thanks.
Jerry
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82595
--- Comment #1 from Andrew Pinski ---
Looks like:
https://gcc.gnu.org/ml/gcc-patches/2013-02/msg01043.html
is no longer part of the sources due to the last merge.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82595
Bug ID: 82595
Summary: bootstrap fails in libsanitizer on
powerpc64-unknown-linux-gnu
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Keywords: build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82569
Eric Botcazou changed:
What|Removed |Added
Status|WAITING |ASSIGNED
Assignee|unassigned
Hello world,
this patch fixes a regression with long compile times,
which came about due to our handling of array constructors
at compile time. This, togeteher with a simplification in
front end optimization, led to long compile times and large
code.
Regression-tested. OK for trunk and the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82594
Andrew Pinski changed:
What|Removed |Added
Keywords||diagnostic
On 14/10/17 16:32, Oren Ben-Kiki wrote:
Thanks for the pointers. I'm not currently using auto tools, but I might
end up having to use them, or cmake. Having these macros would help. I
still wish we had `-Wno-unknown-warnings` though - it would make life much
simpler.
Despite the feedback that
version 8.0.0 20171017):
~~~
$ /opt/gcc/bin/g++ mismatch.cc -c -o mismatch
mismatch.cc: In function ‘void initialize()’:
mismatch.cc:12:35: error: cannot convert ‘void (*)(S2*)’ to ‘S1*’ for argument
‘1’ to ‘void set_delete_thread(S1*, void (*)(S2*))’
set_delete_thread (delete_thread
Andrew MacLeod writes:
> On 10/17/2017 08:18 AM, Richard Sandiford wrote:
>> Aldy Hernandez writes:
>>> Hi folks!
>>>
>>> Calling print_hex() on a widest_int with the most significant bit turned
>>> on can lead to a leading zero being printed (0x0).
On 13/10/17 02:47, Martin Sebor wrote:
[*] We wrote a script scrape those off the online HTML manual
and create a "database" mapping options to GCC versions they
were introduced in (or first documented in, as not every option
always gets documented as it gets added).
I don't understand why you
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82556
--- Comment #5 from Jakub Jelinek ---
Indeed started with my r253710. If there is something wrong on the constraints
on the patterns, please let me know.
Hello,
On Fri, Oct 13, 2017 at 1:18 PM, Geoff Wozniak wrote:
> The code structure suggests that we should
> either do an IPA pass on GIMPLE or we work as an assembler pass, thus
> forgoing work on RTL at all. Is this is what we should be doing?
When I first looked at the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82593
--- Comment #1 from Antonio Ospite ---
Created attachment 42387
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42387=edit
Parenthesized array member initializer with enum as indices
Adding a more concise test program.
Using an array of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82593
Bug ID: 82593
Summary: Internal compiler error: in
process_init_constructor_array, at cp/typeck2.c:1294
Product: gcc
Version: unknown
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82554
--- Comment #4 from Jonathan Wakely ---
Almost all of it is saying things you *don't need to do*.
You just need to send an email.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66802
Jonathan Wakely changed:
What|Removed |Added
Last reconfirmed|2015-07-08 00:00:00 |2017-10-17
--- Comment #2 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82589
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82587
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
On Oct 13, 2017, Richard Biener wrote:
> If the [SFN] is self-contained you can install that part once the approval
> for the FE parts is in.
It is, so I'll do that.
> You can of course wait a bit for more reviews
> (stopped short on LVU because of that all-targets
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56456
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
---
Tested on visium-elf, applied on the mainline and 7 branch.
2017-10-17 Eric Botcazou
* gcc.dg/attr-alloc_size-11.c: UnXFAIL for visium-*-*.
--
Eric BotcazouIndex: gcc.dg/attr-alloc_size-11.c
===
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58150
Eric Gallager changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82542
--- Comment #10 from Eric Gallager ---
(In reply to Ben Longbons from comment #9)
> The ones I've filed are: #54533, #58150, #80466
>
> But there are quite a few more at
>
The compare-elim.c change broke the build because the pass now sends all kind
of junk RTXes to the select_cc_mode target hook, which was written in exact
keeping with arithmetic patterns of the MD file. We now need to handle all
possible RTXes on the RHS of an assignment, even calls.
Tested
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43119
Eric Gallager changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
Are we in agreement that I should revert the patch?
-Original Message-
From: Richard Biener [mailto:richard.guent...@gmail.com]
Sent: Tuesday, October 17, 2017 1:10 PM
To: Michael Collison ; Eric Botcazou
Cc: Jeff Law ;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64611
J. van Oosten changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #9 from J. van
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64611
--- Comment #8 from J. van Oosten ---
Confirmed it works as expected with GCC 5.4.0
> This change broke Ada bootstrap, because the FE doesn't have any tree_size
> langhook, but has one language specific tcc_type tree -
> UNCONSTRAINED_ARRAY_TYPE.
There should be a requirement to test all languages for this kind of changes.
> Fixed thusly, bootstrapped/regtested on x86_64-linux
On October 17, 2017 9:08:31 PM GMT+02:00, Michael Collison
wrote:
>Richard and Eric,
>
>I see you have objected and indicated the additional cost. Have you
>quantified how much more expensive the pass is?
DF has known quadratic behavior in memory for certain problems.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82592
Bug ID: 82592
Summary: [8 Regression] ICE in extract_constrain_insn, at
recog.c:2207 (error: insn does not satisfy its
constraints)
Product: gcc
Version: 8.0
On October 17, 2017 9:29:46 PM GMT+02:00, Jakub Jelinek
wrote:
>Hi!
>
>On Fri, Oct 13, 2017 at 02:29:40PM -0400, Nathan Sidwell wrote:
>> [Although I filed this as a middle-end bug, it's really a core infra
>bug,
>> not sure who the best reviewer is]
>
>> 2017-10-13 Nathan
On Tue, 17 Oct 2017, David Malcolm wrote:
> It also adds generalizes some of the code for this (and for the "std::"
> namespace hints in the C++ frontend), moving it to a new
> c-family/known-headers.cc and .h, and introducing a class known_headers.
> This currently just works by scanning a
> I see you have objected and indicated the additional cost. Have you
> quantified how much more expensive the pass is?
No, but use-def chains are known to be slow because DF is slow, see e.g. the
comment located a few lines below the call to try_merge_compare:
/* ??? This is one point at
The C front-end parts of this patch are OK.
--
Joseph S. Myers
jos...@codesourcery.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58601
Bug 58601 depends on bug 71821, which changed state.
Bug 71821 Summary: [6/7/8 regression] ICE on invalid C++11 code (incorrect
argument for alignas): unexpected expression ‘f’ of kind template_id_expr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71821
Paolo Carlini changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71821
--- Comment #6 from paolo at gcc dot gnu.org ---
Author: paolo
Date: Tue Oct 17 19:49:06 2017
New Revision: 253828
URL: https://gcc.gnu.org/viewcvs?rev=253828=gcc=rev
Log:
2017-10-17 Paolo Carlini
PR
Tested on Linux-PPC64. The debug mode fixes have been tested manually
and individually on Linux-x64.
2017-10-17 Ville Voutilainen
Deduction guides for associative containers, debug mode deduction
guide fixes.
* include/bits/stl_algobase.h (__iter_key_t)
The format_warning_at_substring API has a rather clunk way of indicating
the location of the pertinent param (if any): a source_range * is passed
in, which can be NULL. Doing so requires extracting a range from the
location_t and passing around a pointer to it, or NULL, as needed.
This patch
On 10/15/2017 11:59 PM, Sebastian Huber wrote:
gcc/
* invoke.texi (ffunction-sections and fdata-sections): Update.
---
gcc/doc/invoke.texi | 32
1 file changed, 20 insertions(+), 12 deletions(-)
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71368
--- Comment #1 from paolo at gcc dot gnu.org ---
Author: paolo
Date: Tue Oct 17 19:36:49 2017
New Revision: 253826
URL: https://gcc.gnu.org/viewcvs?rev=253826=gcc=rev
Log:
2017-10-17 Paolo Carlini
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71368
Paolo Carlini changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
Hi!
While we have a warning for falling through out of a noreturn function
or return in such function, the actual UB occurs only if we actually
return from those functions.
This patch attempts to instrument it. Will need to submit the libsanitizer
part upstream first though.
2017-10-17 Jakub
Hi!
On Mon, Oct 16, 2017 at 08:52:50PM +0200, Jakub Jelinek wrote:
> The following patch is an attempt at libsanitizer merge from upstream.
> Sadly libubsan has several ABI incompatible changes, dunno if we should
> fight the mess and re-add backward compatibility back, or as the patch
> does
Hi!
On Fri, Oct 13, 2017 at 02:29:40PM -0400, Nathan Sidwell wrote:
> [Although I filed this as a middle-end bug, it's really a core infra bug,
> not sure who the best reviewer is]
> 2017-10-13 Nathan Sidwell
>
> PR middle-end/82546
> gcc/
> * tree.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71251
--- Comment #5 from Paolo Carlini ---
Related to PR71220.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82478
--- Comment #4 from Corey Tabaka ---
Ah, you are right. Late night mixup...
The outer class friend should work though, correct?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70377
Paolo Carlini changed:
What|Removed |Added
Target Milestone|--- |6.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70377
Paolo Carlini changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67735
Paolo Carlini changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
Richard and Eric,
I see you have objected and indicated the additional cost. Have you quantified
how much more expensive the pass is?
-Original Message-
From: Richard Biener [mailto:richard.guent...@gmail.com]
Sent: Tuesday, October 17, 2017 4:45 AM
To: Eric Botcazou
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65970
Paolo Carlini changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
CC|jason at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82569
--- Comment #5 from seurer at gcc dot gnu.org ---
Created attachment 42385
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42385=edit
test case that shows the problem
This is a cut down single function test case that shows the problem. I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64611
Paolo Carlini changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82591
Bug ID: 82591
Summary: [8 Regression] [graphite] Compile-time hog w/ -O2
-floop-nest-optimize
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Keywords:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82590
Bug ID: 82590
Summary: auto-host.h error: declaration does not declare
anything
Product: gcc
Version: 7.2.0
Status: UNCONFIRMED
Severity: normal
The attached patch has a comment that explains what is going on.
Bootstrapped and regtested on FC23/x86_64 - OK for trunk and 7-branch?
Paul
2017-10-17 Paul Thomas
PR fortran/82550
* expr.c (gfc_check_pointer_assign): A use associated procedure
target in a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82586
Paul Thomas changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |pault at gcc dot gnu.org
---
These is the forth major contribution of X86 intrinsic equivalent
headers for PPC64LE.
X86 SSE2 technology adds double float (__m128d) support, filled in a
number 128-bit vector integer (__m128i) operations and added some MMX
conversions to and from 128-bit vector (XMM) operations.
In general
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82554
--- Comment #3 from Ben Longbons ---
There is DR2524 for the [0, 1) case. Otherwise, filing bugs there looks really
complicated.
I've given you a reproducer. That's as much as I'm capable of.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82542
--- Comment #9 from Ben Longbons ---
The ones I've filed are: #54533, #58150, #80466
But there are quite a few more at
https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=__open__=debug_id=190134=gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82589
--- Comment #1 from G. Steinmetz ---
These variants are processed without any complaints :
$ cat z2.f90
module m
type t(a)
integer, len, private :: a
end type
end
program p
use m
type(t(:)), allocatable ::
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82589
Bug ID: 82589
Summary: ICE in gfc_get_pdt_instance, at fortran/decl.c:3278
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82588
Martin Sebor changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82588
Bug ID: 82588
Summary: missing -Warray-bounds on a excessively large index
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82587
Bug ID: 82587
Summary: ICE in get_pdt_constructor, at fortran/resolve.c:1185
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81404
--- Comment #5 from David Malcolm ---
Candidate patch:
https://gcc.gnu.org/ml/gcc-patches/2017-10/msg01083.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82586
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
Hi Carl,
On Tue, Oct 17, 2017 at 09:56:43AM -0700, Carl Love wrote:
> gcc/ChangeLog:
>
> 2017-10-17 Carl Love
>
> * config/rs6000/rs6000-c.c (P8V_BUILTIN_VEC_REVB):
> Add power 8 definitions for the builtin instances.
> (P9V_BUILTIN_VEC_REVB): Remove the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82586
--- Comment #1 from G. Steinmetz ---
Other invalid snippets :
$ cat z2.f90
program p
type t(a
integer, kind :: a
real(a) :: x
end type
end
$ cat z3.f90
program p
type t(a, a)
integer, kind :: a
This patch depends on:
* "[PATCH] c-family: add name_hint/deferred_diagnostic (v2)"
* https://gcc.gnu.org/ml/gcc-patches/2017-10/msg01021.html
(waiting review)
* [PATCH 3/3] C: hints for missing stdlib includes for macros and types
* https://gcc.gnu.org/ml/gcc-patches/2017-07/msg00125.html
1 - 100 of 240 matches
Mail list logo