Re: gdb 8.x - g++ 7.x compatibility

On 2018-02-07 12:30, Jonathan Wakely wrote: Ah ok, the class name appears mangled in other entities' mangled name. But from what I understand there's no mangled name for the class such that echo | c++filt outputs the class name (e.g. "Foo<10>"). That wouldn't make sense, since there's

Re: gcc 7.3: Replacing global operator new/delete in shared libraries

On 02/06/2018 03:56 PM, Paul Smith wrote: Hi all. Hopefully this isn't too annoying a question :). My environment has been using GCC 6.2 (locally compiled) on GNU/Linux systems. We use a separate heap management library (jemalloc) rather than the libc allocator. The way we did this in the

Re: gdb 8.x - g++ 7.x compatibility

On 02/07/2018 12:11 PM, Daniel Berlin wrote: Note that the ABI is explicitly designed so that type identity can be done by address comparison. correct, but be aware that lots of dynamic objects seem to step outside the ABI by building shared objects with -Bsymbolic[1], or the equivalent

Re: gcc 7.3: Replacing global operator new/delete in shared libraries

On 7 February 2018 at 23:38, Martin Sebor wrote: > On 02/06/2018 03:56 PM, Paul Smith wrote: >> >> Hi all. >> >> Hopefully this isn't too annoying a question :). >> >> My environment has been using GCC 6.2 (locally compiled) on GNU/Linux >> systems. We use a separate heap management library

Re: gcc 7.3: Replacing global operator new/delete in shared libraries

On Thu, 2018-02-08 at 01:17 +0100, Marc Glisse wrote: > On Wed, 7 Feb 2018, Paul Smith wrote: > > > > My question is, what do I need to do to ensure this behavior > > > > persists if I create a global operator new/delete? > > > > > > > > Is it sufficient to ensure that the symbol for our shared >

Re: gcc 7.3: Replacing global operator new/delete in shared libraries

On Wed, 7 Feb 2018, Paul Smith wrote: My question is, what do I need to do to ensure this behavior persists if I create a global operator new/delete? Is it sufficient to ensure that the symbol for our shared library global new/delete symbols are hidden and not global, using a linker map or

Re: gcc 7.3: Replacing global operator new/delete in shared libraries

On Wed, 2018-02-07 at 16:38 -0700, Martin Sebor wrote: > I'm not sure I see how defining operator new inline can work > unless you recompile the world (i.e., all the DSOs used by > the program, including libstdc++). As Marc already hinted, > if libstdc++ dynamically allocates an object using the

gcc-6-20180207 is now available

Snapshot gcc-6-20180207 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/6-20180207/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 6 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-6

Re: gdb 8.x - g++ 7.x compatibility

> "Dan" == Daniel Berlin writes: Dan> If there are multiple types named Foo<2u>, DWARF needs to be extended to Dan> allow a pointer from the vtable debug info to the class type debug info Dan> (unless they already added one). This is what we did for Rust. Rust doesn't

Re: GCC 8.0.0 status on x86_64-w64-mingw32, some issues

> Indeed, this solves most of the new failures. Here is the acats test > summary: > === acats Summary === > # of expected passes 2298 > # of unexpected failures 22 > *** FAILURES: c23003b c23003g c23003i c250002 c380004 cd2b11a cd2b15c > ce2102l ce2102m ce2103a ce2103b

Re: Resolving LTO symbols for static library boundary

On Dienstag, 6. Februar 2018 01:01:29 CET Jan Hubicka wrote: > Dne 2018-02-05 18:44, Richard Biener napsal: > > On February 5, 2018 12:26:58 PM GMT+01:00, Allan Sandfeld Jensen > > > > wrote: > >> Hello GCC > >> > >> In trying to make it possible to use LTO for distro-builds

Re: gcc 7.3: Replacing global operator new/delete in shared libraries

On Tue, 6 Feb 2018, Paul Smith wrote: My environment has been using GCC 6.2 (locally compiled) on GNU/Linux systems. We use a separate heap management library (jemalloc) rather than the libc allocator. The way we did this in the past was to declare operator new/delete (all forms) as inline

Re: GCC 8.0.0 status on x86_64-w64-mingw32, some issues

Am 06.02.2018 um 22:50 schrieb Eric Botcazou: >> Here's a short status report for trunk on x86_64-w64-mingw32 host. >> >> I know this is only a secondary platform, but there are some serius issues. >> >> Especially the ada part is in a bad shape compared to 7.3.0, see >>

Re: gdb 8.x - g++ 7.x compatibility

On 2018-02-07 02:21, Daniel Berlin wrote: As the person who, eons ago, wrote a bunch of the the GDB code for this C++ ABI support, and as someone who helped with DWARF support in both GDB and GCC, let me try to propose a useful path forward (in the hopes that someone will say "that's

Re: gcc 7.3: Replacing global operator new/delete in shared libraries

On Wed, 2018-02-07 at 11:32 +0100, Marc Glisse wrote: > On Tue, 6 Feb 2018, Paul Smith wrote: > > > My environment has been using GCC 6.2 (locally compiled) on > > GNU/Linux systems. We use a separate heap management library > > (jemalloc) rather than the libc allocator. The way we did this in

Re: gdb 8.x - g++ 7.x compatibility

On 02/07/2018 02:44 PM, Simon Marchi wrote: On 2018-02-07 02:21, Daniel Berlin wrote: As the person who, eons ago, wrote a bunch of the the GDB code for this C++ ABI support, and as someone who helped with DWARF support in both GDB and GCC, let me try to propose a useful path forward (in the

Re: gdb 8.x - g++ 7.x compatibility

On 7 February 2018 at 15:07, Manfred wrote: > > > On 02/07/2018 02:44 PM, Simon Marchi wrote: >> >> On 2018-02-07 02:21, Daniel Berlin wrote: >>> >>> As the person who, eons ago, wrote a bunch of the the GDB code for this >>> C++ >>> ABI support, and as someone who helped with

Re: gdb 8.x - g++ 7.x compatibility

On 4 February 2018 at 05:01, Simon Marchi wrote: > On 2018-02-03 13:35, Manfred wrote: >> n4659 17.4 (Type equivalence) p1.3: >> >> Two template-ids refer to the same class, function, or variable if >> ... >> their corresponding non-type template arguments of integral or >> enumeration type have

Re:Re: [gcc plugin] get member offset in struct just like offsetof

Hi Eric, Thank you very much. Your advise is exact right. :) The function bit_position and byte_position is what I want to implement offsetof. Regards At 2018-02-07 00:58:17, "Eric Botcazou" wrote: >> I am writing a gcc plugin for parsing the structure fields. But I

Re: gdb 8.x - g++ 7.x compatibility

On 2/7/2018 4:15 PM, Jonathan Wakely wrote: On 7 February 2018 at 15:07, Manfred wrote: On 02/07/2018 02:44 PM, Simon Marchi wrote: [...] This addresses the issue of how to do good software design in GDB to support different producers cleanly, but I think we have

Re: gdb 8.x - g++ 7.x compatibility

Hi, On Wed, 7 Feb 2018, Simon Marchi wrote: > This addresses the issue of how to do good software design in GDB to > support different producers cleanly, but I think we have some issues > even before that, like how to support g++ 7.3 and up. I'll try to > summarize the issue quickly. It's

Re: gdb 8.x - g++ 7.x compatibility

On 2018-02-07 11:26, Michael Matz wrote: Hi, On Wed, 7 Feb 2018, Simon Marchi wrote: This addresses the issue of how to do good software design in GDB to support different producers cleanly, but I think we have some issues even before that, like how to support g++ 7.3 and up. I'll try to

Re: gdb 8.x - g++ 7.x compatibility

On 7 February 2018 at 16:36, Simon Marchi wrote: > On 2018-02-07 11:26, Michael Matz wrote: >> >> Hi, >> >> On Wed, 7 Feb 2018, Simon Marchi wrote: >> >>> This addresses the issue of how to do good software design in GDB to >>> support different producers cleanly, but I think we have some issues

Re: gdb 8.x - g++ 7.x compatibility

On Wed, Feb 7, 2018 at 5:44 AM, Simon Marchi wrote: > On 2018-02-07 02:21, Daniel Berlin wrote: > >> As the person who, eons ago, wrote a bunch of the the GDB code for this >> C++ >> ABI support, and as someone who helped with DWARF support in both GDB and >> GCC, let me

Re: gdb 8.x - g++ 7.x compatibility

On 7 February 2018 at 17:03, Simon Marchi wrote: > On 2018-02-07 11:50, Jonathan Wakely wrote: >> >> On 7 February 2018 at 16:36, Simon Marchi wrote: >>> >>> On 2018-02-07 11:26, Michael Matz wrote: Hi, On Wed, 7 Feb 2018, Simon Marchi wrote:

Re: gdb 8.x - g++ 7.x compatibility

> > > This avoids the problem of the demangler gdb is using getting a different > name than the producer used. It also should always give you the right one. > If the producer calls the type "vtable fo Foo<2u>" here and "Foo<2>" > elsewhere, yes, that's a bug. It should be consistent. > > This

Announce: GNU MPFR 4.0.1 is released

GNU MPFR 4.0.1 ("dinde aux marrons", patch level 1), a C library for multiple-precision floating-point computations with correct rounding, is now available for download from the MPFR web site: http://www.mpfr.org/mpfr-4.0.1/ from InriaForge: https://gforge.inria.fr/projects/mpfr/ and from

Re: gdb 8.x - g++ 7.x compatibility

On 2018-02-07 11:50, Jonathan Wakely wrote: On 7 February 2018 at 16:36, Simon Marchi wrote: On 2018-02-07 11:26, Michael Matz wrote: Hi, On Wed, 7 Feb 2018, Simon Marchi wrote: This addresses the issue of how to do good software design in GDB to support different producers cleanly, but I

Re: gdb 8.x - g++ 7.x compatibility

On 2018-02-07 12:08, Jonathan Wakely wrote: Why would they not have a mangled name? Interesting. What do they look like, and in what context do they appear? Anywhere you need a name for linkage purposes, such as in a function signature, or as a template argument of another type, or in the

Re: gdb 8.x - g++ 7.x compatibility

On 7 February 2018 at 17:20, Simon Marchi wrote: > On 2018-02-07 12:08, Jonathan Wakely wrote: >> >> Why would they not have a mangled name? >> >>> Interesting. What do they look like, and in what context do they appear? >> >> >> Anywhere you need a name for linkage

Re: gdb 8.x - g++ 7.x compatibility

On Wed, 7 Feb 2018, Simon Marchi wrote: On 2018-02-07 12:08, Jonathan Wakely wrote: Why would they not have a mangled name? Interesting. What do they look like, and in what context do they appear? Anywhere you need a name for linkage purposes, such as in a function signature, or as a

Re: Copyright Assignment

On 05/02/18 22:01 +0100, Tim van Deurzen wrote: Hi, I've written to this list previously to mention I'm working on implementing p0515 (the spaceship operator) for C++. Although I'm still far from finished I'd like to make sure that when I am, I will be able to contribute my changes to GCC.

Re: Copyright Assignment

On 07/02/18 12:16 +, Jonathan Wakely wrote: On 05/02/18 22:01 +0100, Tim van Deurzen wrote: Hi, I've written to this list previously to mention I'm working on implementing p0515 (the spaceship operator) for C++. Although I'm still far from finished I'd like to make sure that when I am, I

Re: C++ PATCH to fix ICE with vector expr folding (PR c++/83659)

On Wed, Feb 7, 2018 at 12:54 PM, Marek Polacek wrote: > On Wed, Feb 07, 2018 at 12:26:04PM -0500, Jason Merrill wrote: >> On Fri, Jan 26, 2018 at 6:22 PM, Jakub Jelinek wrote: >> > On Fri, Jan 26, 2018 at 02:11:19PM +0100, Richard Biener wrote: >> >> >>

Re: [SFN+LVU+IEPM v4 7/9] [LVU] Introduce location views

On 02/06/2018 11:02 PM, Alexandre Oliva wrote: On Feb 6, 2018, Jason Merrill wrote: On 12/11/2017 09:52 PM, Alexandre Oliva wrote: Why do we need to use a non-zero view identifier for a zero view? Why can't we always use 0 instead of the bitmap? We assign view ids

Re: [PATCH] C++: avoid most reserved words as misspelling suggestions (PR c++/81610 and PR c++/80567)

On Wed, 2018-02-07 at 13:22 -0500, Jason Merrill wrote: > On Wed, Feb 7, 2018 at 1:12 PM, David Malcolm > wrote: > > On Wed, 2018-02-07 at 12:21 -0500, Jason Merrill wrote: > > > On Fri, Jan 26, 2018 at 1:12 PM, David Malcolm > > om> > > > wrote: > > > >

[Bug fortran/84270] New: optimization bug with assumed size array argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84270 Bug ID: 84270 Summary: optimization bug with assumed size array argument Product: gcc Version: 7.3.1 Status: UNCONFIRMED Severity: normal Priority: P3

[PATCH] add -Wstringop-overflow to LTO options (PR 84212)

In PR 84212 the reporter asks why -Wno-stringop-overflow has no effect during LTO linking. It turns out that the reason is the same as in bug 78768: the specification in the c.opt file is missing LTO among the languages. The attached patch adds LTO to it and to -Wstringop-truncation.

Re: [PATCH] C++: avoid most reserved words as misspelling suggestions (PR c++/81610 and PR c++/80567)

On Wed, 2018-02-07 at 12:21 -0500, Jason Merrill wrote: > On Fri, Jan 26, 2018 at 1:12 PM, David Malcolm > wrote: > > On Mon, 2017-12-11 at 17:24 -0500, Jason Merrill wrote: > > > On Wed, Nov 22, 2017 at 10:36 AM, David Malcolm > > com> > > > wrote: > > >

[PATCH][GCC][ARM] Silence more re-definition warnings, make test case failure case more explicit.

Hi All, The previous testcase would fail on a system where the initial mode is thumb and later switches to an arm mode. This would again cause some warnings to be emitted. This patch visits all builtins defined with builtin_define_with_int_value and undefines them if they could possibly change

Re: [openacc, committed] Fix diff_type in expand_oacc_collapse_init

Hi Tom, > this patch fixes an 8 regression in an openacc testcase. > > The regression was introduced by r250925, a fix for PR78266, a bug in the > handling of a loop with iteration variable type range smaller than the size > of the parallel dimension the loop is assigned to. > > The fix for the

[Bug target/84266] mmintrin.h intrinsic headers for PowerPC code fails on power9

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84266 --- Comment #2 from Bill Schmidt --- I wonder how many failures are left if that invalid cast is removed from the code? It is just wrong and unnecessary.

Re: [PATCH] C++: avoid most reserved words as misspelling suggestions (PR c++/81610 and PR c++/80567)

On Wed, Feb 7, 2018 at 1:12 PM, David Malcolm wrote: > On Wed, 2018-02-07 at 12:21 -0500, Jason Merrill wrote: >> On Fri, Jan 26, 2018 at 1:12 PM, David Malcolm >> wrote: >> > On Mon, 2017-12-11 at 17:24 -0500, Jason Merrill wrote: >> > > On Wed, Nov 22,

[Bug preprocessor/81419] GCC wrongly suggests function-like macro as fixit hint for undefined object-like macro

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81419 David Malcolm changed: What|Removed |Added Status|NEW |ASSIGNED CC|

Re: C++ PATCH to fix ICE with vector expr folding (PR c++/83659)

On Wed, Feb 07, 2018 at 12:26:04PM -0500, Jason Merrill wrote: > On Fri, Jan 26, 2018 at 6:22 PM, Jakub Jelinek wrote: > > On Fri, Jan 26, 2018 at 02:11:19PM +0100, Richard Biener wrote: > >> >> POINTER_PLUS_EXPR offets are to be interpreted as signed (ptrdiff_t) > >> >> so

Re: [PATCH, rs6000] fix vsxcopy test for power9

Hi, On Wed, Feb 07, 2018 at 10:59:46AM -0600, Will Schmidt wrote: > Noted during review of test results on P9. The vsxcopy.c test is looking > for lxvd2x, stxvd2x instructions in generated code. For P9 targets, we will > instead generate lxv, stxv instructions. > Thus, update the test to handle

[PATCH v6] aarch64: Add split-stack support

Changes from previous version: - Changed the wait to call __morestack to use use a branch with link instead of a simple branch. This allows use a call instruction and avoid possible issues with later optimization passes which might see a branch outside the instruction block (as

[Bug c++/81610] [8 Regression] bogus fix-it hint for a call to an undeclared function: for

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81610 --- Comment #4 from David Malcolm --- Author: dmalcolm Date: Wed Feb 7 17:55:54 2018 New Revision: 257456 URL: https://gcc.gnu.org/viewcvs?rev=257456=gcc=rev Log: C++: avoid most reserved words as misspelling suggestions (PR c++/81610 and PR

[Bug c++/80567] [8 Regression] bogus fixit hint for undeclared memset: else

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80567 --- Comment #7 from David Malcolm --- Author: dmalcolm Date: Wed Feb 7 17:55:54 2018 New Revision: 257456 URL: https://gcc.gnu.org/viewcvs?rev=257456=gcc=rev Log: C++: avoid most reserved words as misspelling suggestions (PR c++/81610 and PR

[Bug c++/81610] [8 Regression] bogus fix-it hint for a call to an undeclared function: for

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81610 David Malcolm changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c++/80567] [8 Regression] bogus fixit hint for undeclared memset: else

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80567 David Malcolm changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c++/84269] New: C++ FE does not suggest which #include to use for "memset"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84269 Bug ID: 84269 Summary: C++ FE does not suggest which #include to use for "memset" Product: gcc Version: 8.0 Status: UNCONFIRMED Severity: normal

[Bug c++/84269] C++ FE does not suggest which #include to use for "memset"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84269 David Malcolm changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

Re: C++ PATCH to fix ICE with vector expr folding (PR c++/83659)

On Wed, Feb 07, 2018 at 01:23:49PM -0500, Jason Merrill wrote: > On Wed, Feb 7, 2018 at 12:54 PM, Marek Polacek wrote: > > On Wed, Feb 07, 2018 at 12:26:04PM -0500, Jason Merrill wrote: > >> On Fri, Jan 26, 2018 at 6:22 PM, Jakub Jelinek wrote: > >> > On

[Bug c++/84269] C++ FE does not suggest which #include to use for "memset"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84269 David Malcolm changed: What|Removed |Added Priority|P3 |P5

[Bug c++/80567] [8 Regression] bogus fixit hint for undeclared memset: else

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80567 David Malcolm changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug target/83789] __builtin_altivec_lvx fails for powerpc for altivec-4.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83789 --- Comment #4 from Segher Boessenkool --- Kaushik: is this fixed with r256762?

Re: RFA: Sanitize deprecation messages (PR 84195)

On Wed, 2018-02-07 at 17:26 +, Nick Clifton wrote: > Hi Martin, Hi David, > > OK - attached is a new patch that: > > * Replaces control characters with their escape equivalents. > * Includes a testcase. > > I was not sure what to do about the inconsistencies between the > behaviour of

[Bug target/84220] rs6000 builtin __builtin_vec_sld() ICEs on invalid 3rd argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84220 Peter Bergner changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED URL|

Re: [PATCH, rs6000] Update vsx-vector-6-le.c tests for p9 target

Hi! On Wed, Feb 07, 2018 at 11:16:12AM -0600, Will Schmidt wrote: > Noted during review of test results on P9. Due to changes and improvements, > our codegen is different for this test on power9. > Modified the existing test to target P8, and added a P9 variant with updated > counts. > diff

[Bug lto/84212] -Wno-* does not disable warnings from -flto link stage

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84212 Martin Sebor changed: What|Removed |Added Keywords||patch --- Comment #6 from Martin Sebor

Re: [RFC PATCH] avoid applying attributes to explicit specializations (PR 83871)

On 02/06/2018 11:01 PM, Martin Sebor wrote: On 02/05/2018 02:52 PM, Jason Merrill wrote: On 02/04/2018 07:07 PM, Martin Sebor wrote: To resolve the underlying root cause of the P1 bug c++/83503 - bogus -Wattributes for const and pure on function template specialization, that we discussed last

[Bug c/84274] New: [feature request] mbind attribute

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84274 Bug ID: 84274 Summary: [feature request] mbind attribute Product: gcc Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug middle-end/84275] New: missing warning on conflicting attributes on different declara

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84275 Bug ID: 84275 Summary: missing warning on conflicting attributes on different declara Product: gcc Version: 8.0 Status: UNCONFIRMED Severity: normal

[PATCH] -Wformat: fix nonsensical "wide character" message (PR c/84258)

PR c/84258 reports that we issue this: warning: format is a wide character string [-Wformat=] on this code: const unsigned char cuc[] = "%i"; sprintf(buf, (char *)cuc, 1); despite the absence of wide characters. This wording dates back 17.5 years to r36586: 2000-09-24 Joseph S. Myers

Re: C++ PATCH to fix ICE with vector expr folding (PR c++/83659)

On Wed, Feb 7, 2018 at 2:48 PM, Jakub Jelinek wrote: > On Wed, Feb 07, 2018 at 08:36:31PM +0100, Marek Polacek wrote: >> > > That was my first patch, but it was rejected: >> > > https://gcc.gnu.org/ml/gcc-patches/2018-01/msg00271.html >> > >> > Then should we update

Re: C++ PATCH to fix ICE with vector expr folding (PR c++/83659)

On Wed, Feb 07, 2018 at 03:23:25PM -0500, Jason Merrill wrote: > On Wed, Feb 7, 2018 at 2:48 PM, Jakub Jelinek wrote: > > On Wed, Feb 07, 2018 at 08:36:31PM +0100, Marek Polacek wrote: > >> > > That was my first patch, but it was rejected: > >> > >

libgo patch committed: Don't call funcPC from a function

This patch changes the libgo runtime package to not call funcPC from a function. The escape analysis support is not yet good enough to avoid escaping the argument to funcPC. This causes unnecessary and often harmful memory allocation. E.g., (*cpuProfile).addExtra can be called from a signal

Re: [PATCH] PowerPC PR target/84154, fix floating point to small integer conversion regression

Hi Mike, On Tue, Feb 06, 2018 at 04:34:08PM -0500, Michael Meissner wrote: > Here is the patch reworked. It bootstraps on both little/big endian power8, > and all of the tests run. Can I install this into trunk now, and into GCC 7 > after a soak period (along with the previous patch)? > +;; If

Re: [PATCH] add -Wstringop-overflow to LTO options (PR 84212)

I went ahead and changed all the options on the list below to include LTO and tested the attached patch by configuring with --with-build-config=bootstrap-lto --disable-werror and making profiledbootstrap. Attached, besides the patch, is also the breakdown of warnings. The interesting column is

Re: [PATCH, rs6000] Update vsx-vector-6-le.c tests for p9 target

On Wed, Feb 07, 2018 at 05:23:31PM -0600, Will Schmidt wrote: > > > /* { dg-do compile { target { powerpc64le-*-* && lp64 } } } */ > > > /* { dg-skip-if "" { powerpc*-*-darwin* } } */ > > > /* { dg-require-effective-target powerpc_vsx_ok } */ > > > -/* { dg-options "-mvsx -O2" } */ > > > +/* {

[Bug fortran/84276] New: Invalid error for valid statement function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84276 Bug ID: 84276 Summary: Invalid error for valid statement function Product: gcc Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran

Re: Please accept this commit for the trunk

On Feb 5, 2018, at 8:42 AM, Douglas Mencken wrote: > > I’m about > > “ [PATCH 2/4] [Darwin,PPC] Remove uses of LR in > restore_world ” https://gcc.gnu.org/bugzilla/attachment.cgi?id=42304 > > look at bug #84113 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113 for >

Re: [PATCH], Document the PowerPC --with-long-double-format={ibm,ieee} configuration options

On Wed, Feb 07, 2018 at 05:26:49PM -0600, Segher Boessenkool wrote: > On Wed, Feb 07, 2018 at 05:48:26PM -0500, Michael Meissner wrote: > > This patch udpates the GCC installation documentation to document the > > configuration options to set the long double type on the PowerPC: I verified > >

[Bug fortran/84276] Invalid error for valid statement function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84276 --- Comment #1 from Steve Kargl --- Reduced testcase. subroutine stepns(hh,h,s,w) real, intent(inout) :: h,hh,s real, intent(out) :: w real :: qofs qofs(s)=s w=qofs(hh+h) end subroutine stepns Problem

Re: [RFC][PR82479] missing popcount builtin detection

Hi Richard, On 1 February 2018 at 23:21, Richard Biener wrote: > On Thu, Feb 1, 2018 at 5:07 AM, Kugan Vivekanandarajah > wrote: >> Hi Richard, >> >> On 31 January 2018 at 21:39, Richard Biener >>

[Bug fortran/84276] Invalid error for valid statement function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84276 kargl at gcc dot gnu.org changed: What|Removed |Added Priority|P3 |P4 Known to fail|

[Bug c/84258] Bogus -Wformat warning "wide character string" for const unsigned char

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84258 David Malcolm changed: What|Removed |Added Status|ASSIGNED|WAITING --- Comment #4 from David

[Bug fortran/68560] [6/7/8 Regression] The test gfortran.dg/shape_8.f90 now fails when compiled with -flto

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68560 --- Comment #28 from Thomas Koenig --- Author: tkoenig Date: Wed Feb 7 21:08:51 2018 New Revision: 257462 URL: https://gcc.gnu.org/viewcvs?rev=257462=gcc=rev Log: 2018-02-07 Thomas Koenig PR fortran/68560

[Bug fortran/84270] optimization bug with assumed size array argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84270 Harald Anlauf changed: What|Removed |Added CC||anlauf at gmx dot de --- Comment #1

[C++ Patch/RFC] PR 83204 ("[6/7/8 Regression] c++ -std=c++14 ICE in maybe_undo_parenthesized_ref, at cp/semantics.c:1694")

Hi, this is essentially an RFC, I'm still fully analyzing the issue, but since I already have something prima facie reasonable and passing the testsuite I decided to send immediately out what I have, looking for further feedback / help. As fully analyzed by Jakub in the audit trail, for the

[Bug fortran/84273] New: Reject allocatable passed-object dummy argument (proc_ptr_47.f90)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84273 Bug ID: 84273 Summary: Reject allocatable passed-object dummy argument (proc_ptr_47.f90) Product: gcc Version: 8.0 Status: UNCONFIRMED Severity: normal

[Bug c++/82478] Rejects valid access to private member type that should be allowed by friend

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82478 Alexander Zaitsev changed: What|Removed |Added CC||zamazan4ik at tut dot by ---

[Bug c++/84082] [7/8 Regression] ICE with broken template function definition

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84082 --- Comment #6 from Jakub Jelinek --- Author: jakub Date: Wed Feb 7 22:30:51 2018 New Revision: 257466 URL: https://gcc.gnu.org/viewcvs?rev=257466=gcc=rev Log: PR c++/84082 * parser.c (cp_parser_dot_deref_incomplete): New

Re: [patch, fortran] Fix PR 68560

On Wed, Feb 07, 2018 at 09:42:04PM +0100, Thomas Koenig wrote: > Here's an update on the patch - I realized that it is not necessary > to check for the actual argument, it is always present. > > OK for trunk? > Yes. -- Steve

[Bug target/78303] PowerPC vec-init-{1,2,4,5,8,9} tests do not run on -mlittle -maltivec=be

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78303 --- Comment #4 from Segher Boessenkool --- If -maltivec=be is not used, I support removing it. Deprecating it with a warning on use will show if anyone care enough to tell us they do use it ;-)

Re: [PATCH] PR fortran/82049 -- resolve a charlen if possible

Thanks. A version of the patch has been commit to 6-branch, 7-branch, and trunk. One regression down, many more to go. -- steve On Wed, Feb 07, 2018 at 08:10:41AM +, Paul Richard Thomas wrote: > Hi Steve, > > That's OK for trunk and, if you are possessed of the intestinal > fortitude, 6-

[Bug fortran/82049] [6/7/8 Regression] ICE with character(*),parameter array constructor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82049 --- Comment #5 from kargl at gcc dot gnu.org --- Author: kargl Date: Wed Feb 7 21:01:00 2018 New Revision: 257461 URL: https://gcc.gnu.org/viewcvs?rev=257461=gcc=rev Log: 2018-02-07 Steven G. Kargl PR

[Bug target/84272] AddressSanitizer: heap-use-after-free ../../gcc/config/aarch64/cortex-a57-fma-steering.c:519 in fma_node::get_parity()

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84272 Martin Liška changed: What|Removed |Added Priority|P3 |P1 Last reconfirmed|

[Bug fortran/84218] ICE in free_expr0, at fortran/expr.c:451

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84218 Neil Carlson changed: What|Removed |Added CC||neil.n.carlson at gmail dot com ---

Re: C++ PATCH to fix ICE with vector expr folding (PR c++/83659)

On Wed, Feb 07, 2018 at 08:36:31PM +0100, Marek Polacek wrote: > > > That was my first patch, but it was rejected: > > > https://gcc.gnu.org/ml/gcc-patches/2018-01/msg00271.html > > > > Then should we update fold_indirect_ref_1 to use the new code? Is > > there a reason for them to stay out of

New Spanish PO file for 'gcc' (version 8.1-b20180128)

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 Spanish team of translators. The file is available at: http://translationproject.org/latest/gcc/es.po (This file, 'gcc-8.1-b20180128.es.po',

[Bug target/83707] g++.dg/eh/simd-3.C fails on power7 -m32

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83707 --- Comment #3 from Will Schmidt --- Created attachment 43360 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43360=edit .expand dump from a build with -O1. the .expand dump from a build with -O1.

Re: [PATCH, rs6000] fix vsxcopy test for power9

On Wed, 2018-02-07 at 12:02 -0600, Segher Boessenkool wrote: > Hi, > > On Wed, Feb 07, 2018 at 10:59:46AM -0600, Will Schmidt wrote: > > Noted during review of test results on P9. The vsxcopy.c test is looking > > for lxvd2x, stxvd2x instructions in generated code. For P9 targets, we will > >

Re: [PATCH], Document the PowerPC --with-long-double-format={ibm,ieee} configuration options

On Wed, Feb 07, 2018 at 05:48:26PM -0500, Michael Meissner wrote: > This patch udpates the GCC installation documentation to document the > configuration options to set the long double type on the PowerPC: I verified > that the documentation builds. Can I install this on to the trunk? Yes

Re: [patch, fortran] Fix PR 68560

Here's an update on the patch - I realized that it is not necessary to check for the actual argument, it is always present. OK for trunk? Regards Thomas 2018-02-01  Thomas Koenig  PR fortran/68560 * trans-intrinsic.c (gfc_conv_intrinsic_shape): New

[Bug c/83390] valgrind error in lra_eliminate_regs_1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83390 --- Comment #8 from Vladimir Makarov --- (In reply to David Binderman from comment #0) > A build of today's gcc trunk with valgrind produces this: > > ==8995== Conditional jump or move depends on uninitialised value(s) > ==8995==at

Re: [PATCH] libgcc: xtensa: fix build with -mtext-section-literals

On Thu, Feb 1, 2018 at 9:12 AM, Max Filippov wrote: > On Wed, Jan 31, 2018 at 11:17 AM, Max Filippov wrote: >> On Wed, Jan 31, 2018 at 11:11 AM, augustine.sterl...@gmail.com >> wrote: >>> On Tue, Jan 30, 2018 at 8:02 PM, Max

[Bug target/83707] g++.dg/eh/simd-3.C fails on power7 -m32

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83707 Will Schmidt changed: What|Removed |Added CC||willschm at gcc dot gnu.org --- Comment

[PATCH], Document the PowerPC --with-long-double-format={ibm,ieee} configuration options

This patch udpates the GCC installation documentation to document the configuration options to set the long double type on the PowerPC: I verified that the documentation builds. Can I install this on to the trunk? 2018-02-07 Michael Meissner *

  1   2   3   >