[PATCH], Add configuration checks to PowerPC --with-long-double-format=ieee

This patch adds a simple check of whether the GLIBC should be capable of switching the long double format on the PowerPC to IEEE 128-bit floating point. At the moment, library work is not yet finished, but I'm assuming that the patches will be in place when GLIBC 2.28 is released. If it turns out

Re: [PATCH 0/3][POPCOUNT]

On 07/05/2018 11:39 PM, Richard Biener wrote: > On July 6, 2018 12:03:11 AM GMT+02:00, Jeff Law wrote: >> On 06/24/2018 08:41 PM, Kugan Vivekanandarajah wrote: >>> Hi Jeff, >>> >>> Thanks for the comments. >>> >>> On 23 June 2018 at 02:06, Jeff Law wrote: On 06/22/2018 03:11 AM, Kugan

Re: [PATCH 0/3][POPCOUNT]

On July 6, 2018 12:03:11 AM GMT+02:00, Jeff Law wrote: >On 06/24/2018 08:41 PM, Kugan Vivekanandarajah wrote: >> Hi Jeff, >> >> Thanks for the comments. >> >> On 23 June 2018 at 02:06, Jeff Law wrote: >>> On 06/22/2018 03:11 AM, Kugan Vivekanandarajah wrote: When we set niter with

[Bug bootstrap/39849] segfault for '__divtf3' during bootstrap and non-bootstrap install

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39849 Eric Gallager changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

Re: ChangeLog's: do we have to?

On 07/05/2018 05:02 PM, Richard Biener wrote: I assumed you just want to remove the ChangeLog files, not change contents. Thus I assumed the commit message would simply contain the ChangeLog entry as we requie it today? In that case git log --grep would still provide everything grepping

[Bug bootstrap/8477] autoconf script chooses wrong value for gcc_gxx_include_path

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=8477 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org --- Comment

[Bug bootstrap/34818] --with-gmp overrides --with-mpfr

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=34818 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org ---

[Bug bootstrap/38667] gcc 4.3.2 build fails to create/link libgcc in SLES9 32-bit platform

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38667 Eric Gallager changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

[Bug fortran/82721] [7/8/9 Regression] Error message with corrupted text, sometimes ICE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82721 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org

[Bug c++/84733] [8/9 Regression] internal compiler error: Segmentation fault (check_local_shadow())

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84733 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org

[Bug c++/84611] [6/7 Regression] ICE in operator[], at vec.h:826 (local_class_index())

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84611 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org

[Bug c++/84630] [6/7 Regression] ICE: TYPE_NAME() used on error_mark_node in tsubst_lambda_expr, at cp/pt.c:17141

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84630 Eric Gallager changed: What|Removed |Added Severity|normal |minor

[Bug libgcc/62269] m32c-elf libgcc fails to configure- setjmp/longjmp exception check

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62269 --- Comment #2 from DJ Delorie --- Sorry for not being as responsive as I should be, but I've tried occasionally to fix the m32c-gcc issues and they just keep getting worse. I suspect m32c should be deprecated at this point, it's not one of of

[Bug c++/85014] [6/7/8/9 Regression] internal compiler error: in lookup_base, at cp/search.c:185

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85014 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org

[Bug c++/84730] internal compiler error: Segmentation fault (build_class_member_access_expr)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84730 Eric Gallager changed: What|Removed |Added Keywords||error-recovery CC|

[Bug fortran/52622] heap-use-after-free with instrumented compiler

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52622 Eric Gallager changed: What|Removed |Added Keywords||error-recovery CC|

[Bug c++/84653] internal compiler error: Segmentation fault (prep_operand)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84653 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org

[Bug c++/84652] internal compiler error: in cp_parser_template_id, at cp/parser.c:15860

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84652 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org

[Bug c++/84633] internal compiler error: in lvalue_kind, at cp/tree.c:206

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84633 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org

[Bug c++/39751] ICE in cp_lexer_new_from_tokens, at cp/parser.c:342

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39751 Eric Gallager changed: What|Removed |Added Keywords||error-recovery, |

[Bug rtl-optimization/63156] web can't handle AUTOINC correctly

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63156 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org

[Bug libgcc/62269] m32c-elf libgcc fails to configure- setjmp/longjmp exception check

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62269 Eric Gallager changed: What|Removed |Added Keywords||build CC|

[committed] Fix tree-ssa/asm-2.c on the v850

r0 on the v850 is a hardwired 0 value. For reasons unknown I exposed it in the register file. This runs afoul of tree-ssa/asm-2.c which has a local variable explicitly assigned to register 0. This naturally blows up. The fix is trivial, use a different register like other ports do.

[Bug preprocessor/44317] ,##__VA_ARGS__ comma not eaten with -std=c++0x

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44317 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org

[Bug tree-optimization/86010] [7/8/9 Regression] redundant memset with smaller size not eliminated

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86010 --- Comment #5 from Jeffrey A. Law --- Author: law Date: Fri Jul 6 03:43:42 2018 New Revision: 262464 URL: https://gcc.gnu.org/viewcvs?rev=262464=gcc=rev Log: PR tree-optimization/86010 * tree-ssa-dse.c (compute_trims): More

[committed] [PR tree-optimization/86010] More aggressively trim partially dead mem* and str* calls

As noted in BZ 86010 we can be more aggressive when trimming tails of mem* or str* calls in gimple DSE since trimming a tail doesn't affect alignment and residuals are usually handled pretty efficiently in libc. Additionally, if the total number of live bytes left is smaller than a word, then

Re: [PATCH] Update config.guess and config.sub

On 07/05/2018 09:18 PM, Jim Wilson wrote: > On Thu, Jul 5, 2018 at 12:22 PM, Liviu Ionescu wrote: >>> On 5 Jul 2018, at 22:17, Jim Wilson wrote: >>> ... I can fix the gcc config.sub to make it work. >> Or you can edit `gcc/config.gcc` and trigger an error for `riscv-linux*`. > > I added patches

Re: [PATCH] Update config.guess and config.sub

On Thu, Jul 5, 2018 at 12:22 PM, Liviu Ionescu wrote: >> On 5 Jul 2018, at 22:17, Jim Wilson wrote: >> ... I can fix the gcc config.sub to make it work. > Or you can edit `gcc/config.gcc` and trigger an error for `riscv-linux*`. I added patches to binutils and gcc to make riscv-elf work.

[PATCH] RISC-V: Add support for riscv-*-*.

Support for riscv-* was added to config.sub upstream, so we need to handle it in gcc configure. Just one place needs to be fixed for now to make this work. Tested with riscv{32,64}-{elf,linux} and riscv-elf cross builds. Committed. Jim gcc/ * config.gcc (riscv*-*-*): When

[Bug c/77817] -Wimplicit-fallthrough: cpp directive renders FALLTHRU comment ineffective

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77817 --- Comment #18 from Anton Maklakov --- Thank you for the answer! I've got. Using the hint after #endif is not pretty good, by the logic. But this is easier.

Re: Inefficient code

> On Jul 5, 2018, at 9:01 PM, Paul Koning wrote: > > > >> On Jul 5, 2018, at 6:47 PM, Eric Botcazou wrote: >> >>> So back to the previous one: anything I can do about a 24 bit field getting >>> split into three movqi rather than a movqi plus a movhi? That happens >>> during RTL expand, I

Re: Inefficient code

> On Jul 5, 2018, at 6:47 PM, Eric Botcazou wrote: > >> So back to the previous one: anything I can do about a 24 bit field getting >> split into three movqi rather than a movqi plus a movhi? That happens >> during RTL expand, I believe. > > Yes, this one doesn't look as hopeless as the

[Bug tree-optimization/86010] [7/8/9 Regression] redundant memset with smaller size not eliminated

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86010 --- Comment #4 from Jeffrey A. Law --- Actually, alignment considerations are really just for head trimming. When trimming the tail we can be more aggressive as residuals are usually handled reasonably efficiently.

Re: [PATCH] fold strlen() of substrings within strings (PR 86415)

On 07/05/2018 05:54 PM, Martin Sebor wrote: > GCC folds strlen() calls to empty substrings within arrays > whose elements are explicitly initialized with NULs but > fails to do the same for elements that are zeroed out > implicitly.  For example: > >   const char a[7] = "123\000\000\000"; >   int 

[Bug tree-optimization/86415] strlen() not folded for substrings within constant arrays

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

[Bug middle-end/77357] strlen of constant strings not folded

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

[PATCH] fold strlen() of substrings within strings (PR 86415)

GCC folds strlen() calls to empty substrings within arrays whose elements are explicitly initialized with NULs but fails to do the same for elements that are zeroed out implicitly. For example: const char a[7] = "123\000\000\000"; int f (void) { return strlen (a + 5); // folded }

[PATCH] fold strlen() of aggregate members (PR 77357)

GCC folds accesses to members of constant aggregates except for character arrays/strings. For example, the strlen() call below is not folded: const char a[][4] = { "1", "12" }; int f (void) { retturn strlen (a[1]); } The attached change set enhances the string_constant() function to make

[PATCH, Ada] Makefile patches from initial RISC-V cross/native build.

These are some patches I needed to complete my cross build of a native riscv linux Ada compiler. Some paths were different on the build machine and host machine. I needed to pass options into gnatmake to work around this, and that required fixing some makefile rules to use $(GNATMAKE) instead of

[PATCH, Ada] RISC-V: Initial riscv linux Ada port.

I was asked about Ada support, so I tried cross building a native RISC-V Linux Ada compiler, and it turned out to be possible with a little bit of work. I just started with the MIPS support, and then fixed everything that was obviously wrong: endianness, error numbers, signal numbers,

[Bug tree-optimization/86010] [7/8/9 Regression] redundant memset with smaller size not eliminated

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86010 --- Comment #3 from Jeffrey A. Law --- It's not an off by 1 error, but a conscious decision to not pass odd addresses into the mem* routines, which are typically doing to emit crappy code for badly aligned data. We correctly see that 7 bytes of

-Wclass-memaccess warning should be in -Wextra, not -Wall

Simply because a struct has a constructor does not mean it isn't a viable target/source for use with memcpy/memmove/memset. Having benchmarked the alternatives memcpy/memmove/memset definitely makes a difference in various scenarios. The bypass of littering code with needless reinterpret_cast's

Re: Inefficient code

> So back to the previous one: anything I can do about a 24 bit field getting > split into three movqi rather than a movqi plus a movhi? That happens > during RTL expand, I believe. Yes, this one doesn't look as hopeless as the store merging issue. A way of tackling it would be to do a

gcc-7-20180705 is now available

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

Re: overflow check in extract_range_from_binary_1 useless?

On 06/13/2018 05:18 AM, Richard Biener wrote: > On Fri, Jun 8, 2018 at 11:42 AM Aldy Hernandez wrote: >> >> Howdy. >> >> Am I missing something or are these two sets identical? >> >>> /* Get the lower and upper bounds of the type. */ >>> if (TYPE_OVERFLOW_WRAPS (expr_type)) >>>

Re: [PATCH 0/3][POPCOUNT]

On 06/24/2018 08:41 PM, Kugan Vivekanandarajah wrote: > Hi Jeff, > > Thanks for the comments. > > On 23 June 2018 at 02:06, Jeff Law wrote: >> On 06/22/2018 03:11 AM, Kugan Vivekanandarajah wrote: >>> When we set niter with maybe_zero, currently final_value_relacement >>> will not happen due to

Re: ChangeLog's: do we have to?

> "Florian" == Florian Weimer writes: Florian> To some degree, it's a bit of a chicken-and-egg problem because Florian> “git am” tends to choke on ChangeLog patches (so we can't Florian> really use it today) FWIW, installing a ChangeLog merge driver fixes this. I use git-merge-changelog

[Bug libstdc++/86409] std::stod fails for denormal numbers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86409 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug libstdc++/85831] types should have move constructors and move assignment operators

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85831 Jonathan Wakely changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug libstdc++/85831] types should have move constructors and move assignment operators

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85831 --- Comment #1 from Jonathan Wakely --- Author: redi Date: Thu Jul 5 21:29:51 2018 New Revision: 262456 URL: https://gcc.gnu.org/viewcvs?rev=262456=gcc=rev Log: PR libstdc++/85831 define move constructors and operators for exceptions

[PATCH] PR libstdc++/85831 define move constructors and operators for exceptions

PR libstdc++/85831 * config/abi/pre/gnu.ver: Export move constructors and move assignment operators for std::logic_error and std::runtime_error. * include/std/stdexcept: Use _GLIBCXX_NOTHROW instead of _GLIBCXX_USE_NOEXCEPT. (logic_error,

[Bug target/86394] Broken -falign-functions=512 on m68k

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86394 Jeffrey A. Law changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

[PATCH] doc clarification: DONE and FAIL in define_split and define_peephole2

Currently DONE and FAIL are documented only for define_expand, but they also work in essentially the same way for define_split and define_peephole2. If FAIL is used in a define_insn_and_split, the output pattern cannot be the usual "#" dummy value. This patch updates the doc to describe those

Re: [PATCH] Fix several AVX512 intrinsic mask arguments.

On Thu, Jul 5, 2018 at 9:28 PM, Jakub Jelinek wrote: > On Thu, Jul 05, 2018 at 08:30:27PM +0300, Grazvydas Ignotas wrote: >> gcc/ChangeLog: >> >> 2018-07-05 Grazvydas Ignotas >> >> * config/i386/avx512bwintrin.h: (_mm512_mask_cmp_epi8_mask, >> _mm512_mask_cmp_epu8_mask): Fix mask

Re: Question on -fopt-info-inline

On Thu, 2018-07-05 at 13:04 -0600, Jeff Law wrote: > On 07/05/2018 09:27 AM, Qing Zhao wrote: > > > > > On Jul 3, 2018, at 7:19 PM, Jeff Law > > > wrote: > > > > > > On 07/03/2018 12:28 PM, Qing Zhao wrote: > > > > > > > > > > > > > > > > > > > > > > > > In order to

Re: Inefficient code

> On Jul 5, 2018, at 4:44 PM, Eric Botcazou wrote: > > ... > The GIMPLE pass responsible for the optimization simply punts for the "funny- > endian ordering" of the PDP11. More generally, you shouldn't expect anything > sparkling for such a peculiar architecture as the PDP11. Ok. Yet

[Bug libstdc++/86272] [6/7/8/9 Regression] __gnu_debug::string uses undefined __glibcxx_check_insert_range2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86272 --- Comment #8 from François Dumont --- Author: fdumont Date: Thu Jul 5 20:51:27 2018 New Revision: 262455 URL: https://gcc.gnu.org/viewcvs?rev=262455=gcc=rev Log: 2018-07-05 François Dumont Backport from mainline

[Bug tree-optimization/86415] strlen() not folded for substrings within constant arrays

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86415 Martin Sebor changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug libstdc++/86272] [6/7/8/9 Regression] __gnu_debug::string uses undefined __glibcxx_check_insert_range2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86272 --- Comment #7 from François Dumont --- Author: fdumont Date: Thu Jul 5 20:48:02 2018 New Revision: 262454 URL: https://gcc.gnu.org/viewcvs?rev=262454=gcc=rev Log: 2018-07-05 François Dumont Backport from mainline

[Bug tree-optimization/86415] strlen() not folded for substrings within constant arrays

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86415 Martin Sebor changed: What|Removed |Added Summary|TREE_STRING_LENGTH |strlen() not folded for

Re: Inefficient code

> I just constructed another test case that shows the same issue more > blatantly: > > struct s > { > char a; > char b; > char c; > char d; > int e; > int f; > char h; > char i; > }; No, it's not the same issue. > struct s ts; > > void setts(void) > { >

[Bug fortran/86416] New: [OMPVV SOLLVE] Defaultmap issues on OpenMP 4.5

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86416 Bug ID: 86416 Summary: [OMPVV SOLLVE] Defaultmap issues on OpenMP 4.5 Product: gcc Version: 8.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

Re: [patch] Improve specs processing to allow %* in function arguments

On 06/05/2018 08:13 AM, Olivier Hainque wrote: > Hello, > > The attached patch is a proposal to improve specs processing > so %* works in spec function arguments (it doesn't as of today). > > The immediate motivation is to allow a cleaner implementation of > the -mmacosx-version-min support on

Re: [PATCH] tighten up -Wbuiltin-declaration-mismatch (PR 86125)

On 06/28/2018 09:14 AM, Martin Sebor wrote: > On 06/27/2018 11:20 PM, Jeff Law wrote: >> On 06/26/2018 05:32 PM, Martin Sebor wrote: >>> Attached is an updated patch to tighten up the warning and also >>> prevent ICEs in the middle-end like in PR 86308 or PR 86202. >>> >>> I took Richard's

Re: interrupting Ada tests

Hi Simon, > On 5 Jul 2018, at 20:08, Richard Biener wrote: >> >> On July 5, 2018 6:37:58 PM GMT+02:00, Martin Sebor wrote: >>> Ada tests don't seem to respond to the INT signal: when >>> I interrupt a parallel make check while the Ada tests are >>> running, other test suites are interrupted as

Re: Run (some?) ELF constructors after applying RELRO protection

On 06/11/2018 08:59 PM, Rich Felker wrote: If the application already has to annotate that the data is going to be read-only after ctors, it can just page-align/page-pad the data itself and call mprotect with minimal additional effort, and no complex interaction between application code and

Re: interrupting Ada tests

On 5 Jul 2018, at 20:08, Richard Biener wrote: > > On July 5, 2018 6:37:58 PM GMT+02:00, Martin Sebor wrote: >> Ada tests don't seem to respond to the INT signal: when >> I interrupt a parallel make check while the Ada tests are >> running, other test suites are interrupted as well and go >>

Re: [RFC PATCH] diagnose built-in declarations without prototype (PR 83656)

On 07/04/2018 11:32 AM, Martin Sebor wrote: > On 07/03/2018 08:33 PM, Jeff Law wrote: >> >>> >>> But since the number of warnings here hasn't changed, the ones >>> in GCC logs predate my changes.  So updating the tests seems >>> like an improvement to consider independently of the patch. >>

Re: [PING][PATCH, rs6000, C/C++] Fix PR target/86324: divkc3-1.c FAILs when compiling with -mabi=ieeelongdouble

On 07/02/2018 03:50 PM, Peter Bergner wrote: > I'd like to PING: > > https://gcc.gnu.org/ml/gcc-patches/2018-06/msg01713.html > > I've included the entire patch below, since I missed the test cases in > the original submission and Segher asked for some updated text for the > hook documentation

Re: [PATCH] Prefer mempcpy to memcpy on x86_64 target (PR middle-end/81657).

On 04/10/2018 06:27 AM, Martin Liška wrote: > On 04/10/2018 11:19 AM, Jakub Jelinek wrote: >> On Mon, Apr 09, 2018 at 02:31:04PM +0200, Martin Liška wrote: >>> gcc/testsuite/ChangeLog: >>> >>> 2018-03-28 Martin Liska >>> >>> * gcc.dg/string-opt-1.c: >> I guess you really didn't mean to keep

Re: Invalid program counters and unwinding

On 07/02/2018 06:14 PM, Michael Matz wrote: There is no such language in the psABI, no (at least I haven't found anything; you had me worried for a moment :) ). But there's stronger one: all functions through which unwinding is expected must provide CFI. So, yes, such code isn't strictly

Re: [PATCH][Middle-end]3rd patch of PR78809

On 07/05/2018 09:35 AM, Qing Zhao wrote: > Hi, > > I have sent two emails with the updated patches on 7/3: > > https://gcc.gnu.org/ml/gcc-patches/2018-07/msg00065.html > https://gcc.gnu.org/ml/gcc-patches/2018-07/msg00070.html > > however, these 2 emails  were not successfully forwarded to the

[Bug tree-optimization/86415] New: TREE_STRING_LENGTH incorrect for constant arrays

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86415 Bug ID: 86415 Summary: TREE_STRING_LENGTH incorrect for constant arrays Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

Re: [patch] jump threading multiple paths that start from the same BB

On 07/04/2018 02:12 AM, Aldy Hernandez wrote: > > > On 07/03/2018 08:16 PM, Jeff Law wrote: >> On 07/03/2018 03:31 AM, Aldy Hernandez wrote: >>> On 07/02/2018 07:08 AM, Christophe Lyon wrote: >>> >> On 11/07/2017 10:33 AM, Aldy Hernandez wrote: >>> While poking around in the backwards 

Re: [PATCH] Enable decimal float on x86_64 kFreeBSD and Hurd

On 07/04/2018 03:24 PM, James Clarke wrote: > config/ > * dfp.m4 (enable_decimal_float): Enable for x86_64*-*-gnu* to > catch x86_64 kFreeBSD and Hurd. > > gcc/ > * configure: Regenerate. > > libdecnumber/ > * configure: Regenerate. > > libgcc/ > * configure:

Re: [PATCH] Update config.guess and config.sub

> On 5 Jul 2018, at 22:17, Jim Wilson wrote: > > ... I can fix the gcc config.sub to make it work. Or you can edit `gcc/config.gcc` and trigger an error for `riscv-linux*`. Regards, Liviu

Re: [PATCH] Update config.guess and config.sub

On Thu, Jul 5, 2018 at 11:31 AM, Liviu Ionescu wrote: > If this is really a problem I guess you can blacklist it somehow. > But this proves once again that Linux native compilers and cross embedded > toolchains should be processed differently. It isn't a major problem. There is the issue that

Re: [PATCH] libtool: Sort output of 'find' to enable deterministic builds.

On 07/05/2018 08:53 AM, Bernhard M. Wiedemann wrote: > On 2018-06-29 17:09, Jeff Law wrote: >> In the immediate term, applying the patch to both instances seems wise. >> >> Bernhard, do you have commit privs? > > no, and I dont really want privs, since I expect to be doing only a few > patches

Re: interrupting Ada tests

On July 5, 2018 6:37:58 PM GMT+02:00, Martin Sebor wrote: >Ada tests don't seem to respond to the INT signal: when >I interrupt a parallel make check while the Ada tests are >running, other test suites are interrupted as well and go >away, but ada tests keep running. Is there some trick to >have

Re: Question on -fopt-info-inline

On 07/05/2018 09:27 AM, Qing Zhao wrote: > >> On Jul 3, 2018, at 7:19 PM, Jeff Law > > wrote: >> >> On 07/03/2018 12:28 PM, Qing Zhao wrote: >>> > >> >> In order to collect complete information on all the inlining >> transformation that GCC applies on a

Re: [PATCH] Update config.guess and config.sub

> On 5 Jul 2018, at 21:26, Jim Wilson wrote: > > because it adds riscv-linux as a valid configure tuple, and we never wanted > that If this is really a problem I guess you can blacklist it somehow. But this proves once again that Linux native compilers and cross embedded toolchains should

Re: [PATCH] Fix several AVX512 intrinsic mask arguments.

On Thu, Jul 05, 2018 at 08:30:27PM +0300, Grazvydas Ignotas wrote: > gcc/ChangeLog: > > 2018-07-05 Grazvydas Ignotas > > * config/i386/avx512bwintrin.h: (_mm512_mask_cmp_epi8_mask, > _mm512_mask_cmp_epu8_mask): Fix mask arguments. LGTM, but 1) I think it would be nice to add a

Re: [PATCH] Update config.guess and config.sub

On 07/05/2018 09:51 AM, Palmer Dabbelt wrote: When I try to build it I see "Unsupported RISC-V target riscv-unknown-elf", so there's at least some extra autoconf wizadry that needs to happen in here.  I'm actually not sure what the "riscv-*" tuples are supposed to do so I've added Liviu as I

[Bug c/86414] New: AIX generates wrong

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86414 Bug ID: 86414 Summary: AIX generates wrong Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee:

Re: ChangeLog's: do we have to?

On 7/5/18, Aldy Hernandez wrote: > After 20 years of hacking on GCC I feel like I have literally wasted > days of my life typing out ChangeLog entries that could have easily been > generated programmatically. > > Can someone refresh my memory here, what are the remaining arguments for > requiring

[Bug fortran/83118] [7/8/9 Regression] Bad intrinsic assignment of class(*) array component of derived type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83118 --- Comment #13 from Paul Thomas --- Created attachment 44356 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44356=edit Fix for the new problem? Hi Rainer, Does the attachment fix the problem? Cheers Paul

[PATCH] Fix several AVX512 intrinsic mask arguments.

gcc/ChangeLog: 2018-07-05 Grazvydas Ignotas * config/i386/avx512bwintrin.h: (_mm512_mask_cmp_epi8_mask, _mm512_mask_cmp_epu8_mask): Fix mask arguments. --- gcc/config/i386/avx512bwintrin.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

Re: [PATCH] Update config.guess and config.sub

> On 5 Jul 2018, at 19:51, Palmer Dabbelt wrote: > > ... When I try to build it I see "Unsupported RISC-V target > riscv-unknown-elf", I guess configure is fine, you need to allow for the `riscv-` prefix in gcc/config.gcc, around line 3982 > so there's at least some extra autoconf wizadry

[Bug fortran/86408] [9 Regression] bogus error: ABSTRACT INTERFACE must not have an assumed character length result (F2003: C418)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86408 --- Comment #12 from janus at gcc dot gnu.org --- (In reply to Paul Thomas from comment #11) > Thanks for the heads up Janus. Thanks for the extremely quick fix, Paul! I often wish commercial vendors would even get close to gfortran's turnaround

[Bug ipa/86395] add support of -fopt-info-inline in early inliner

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86395 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org ---

[Bug libstdc++/58265] [lwg/2063] std::string move assignment should be noexcept

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58265 --- Comment #14 from Jonathan Wakely --- Author: redi Date: Thu Jul 5 17:03:05 2018 New Revision: 262447 URL: https://gcc.gnu.org/viewcvs?rev=262447=gcc=rev Log: PR libstdc++/58265 add noexcept to basic_string::assign(basic_string&&)

Re: [PATCH] Update config.guess and config.sub

On 07/05/2018 10:51 AM, Palmer Dabbelt wrote: > On Thu, 05 Jul 2018 05:00:20 PDT (-0700), > sebastian.hu...@embedded-brains.de wrote: >> * config.guess: Sync with upstream version 2018-06-26. >> * config.sub: Sync with upstream version 2018-07-02. >> --- >>  config.guess | 6 +++--- >>  

[PATCH] Add xfail-if to some tests that fail with COW strings

These tests fail when run with -D_GLIBCXX_USE_CXX11_ABI=0 * testsuite/21_strings/basic_string/cons/char/deduction.cc: XFAIL for COW strings. * testsuite/21_strings/basic_string/cons/wchar_t/deduction.cc: Likewise. *

Re: [PATCH] Update config.guess and config.sub

On 07/05/2018 06:00 AM, Sebastian Huber wrote: > * config.guess: Sync with upstream version 2018-06-26. > * config.sub: Sync with upstream version 2018-07-02. OK. And I think in general syncing to the latest version from upstream ought not require explicit approval. Richi/Jakub have

Re: [PATCH] PR libstdc++/58265 implement LWG 2063 for COW strings

On 05/07/18 16:55 +0100, Jonathan Wakely wrote: For COW strings the default constructor does not allocate when _GLIBCXX_FULLY_DYNAMIC_STRING == 0, so can be noexcept. The move constructor and swap do not allocate when the allocators are equal, so add conditional noexcept using

[Bug demangler/85304] Segmentation fault

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85304 Carlo B. changed: What|Removed |Added CC||castro8583bennett at gmx dot com ---

Re: [PATCH] Update config.guess and config.sub

On Thu, 05 Jul 2018 05:00:20 PDT (-0700), sebastian.hu...@embedded-brains.de wrote: * config.guess: Sync with upstream version 2018-06-26. * config.sub: Sync with upstream version 2018-07-02. --- config.guess | 6 +++--- config.sub | 8 +++- 2 files changed, 10

Re: decrement_and_branch_until_zero pattern

> On Jun 8, 2018, at 6:16 PM, Jim Wilson wrote: > > On Fri, Jun 8, 2018 at 1:12 PM, Paul Koning wrote: >> Thanks. I saw those sections and interpreted them as support for signal >> processor style fast hardware loops. If they can be adapted for dbra type >> looping, great. I'll give

[Bug tree-optimization/83819] [meta-bug] missing strlen optimizations

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83819 Bug 83819 depends on bug 86400, which changed state. Bug 86400 Summary: set::sethttps://gcc.gnu.org/bugzilla/show_bug.cgi?id=86400 What|Removed |Added

[Bug tree-optimization/86400] set::set

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86400 Martin Sebor changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

  1   2   3   >