[Bug fortran/97768] [10/11 Regression] 32-bit f951 ICE on code from OpenMolcas

2020-11-09 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97768 --- Comment #1 from Jakub Jelinek --- Seems this is only in the pretty-printing for message that would be printed if there was an error later on (which there is not). So I guess it really doesn't matter that much what exactly it prints, but it sh

[Bug fortran/97768] [10/11 Regression] 32-bit f951 ICE on code from OpenMolcas

2020-11-09 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97768 --- Comment #2 from Jakub Jelinek --- If in the testcase I change the penultimate line to: l = 32 .in. to_upper(str) so that an error is emitted, the 64-bit little-endian f951 emits: Error: Operands of user operator ‘in’ at (1) are INTEGER(4)/C

[Bug pch/56549] #pragma once ineffective with BOM in include file

2020-11-09 Thread julien.ruffin at ivu dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56549 Julien Ruffin changed: What|Removed |Added CC||julien.ruffin at ivu dot de --- Comment

[Bug fortran/97768] [10/11 Regression] 32-bit f951 ICE on code from OpenMolcas

2020-11-09 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97768 Jakub Jelinek changed: What|Removed |Added CC||markeggleston at gcc dot gnu.org --- Co

[Bug fortran/97768] [10/11 Regression] 32-bit f951 ICE on code from OpenMolcas

2020-11-09 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97768 --- Comment #4 from Jakub Jelinek --- Or the length could be e.g. local variable: subroutine baz (lens) use fortran_strings, only : to_upper, operator(.in.) integer :: lens character(len=lens) str logical l str = '' l = 32 .in. to_upp

[Bug debug/97441] gcc writes absolute path to .stabstr section even if fdebug-prefix-map is used

2020-11-09 Thread dzagorui at cisco dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97441 Denys Zahorui changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c/97769] New: [11 Regression] vectorizer ICE when building perlbench in SPECCPU 2017

2020-11-09 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97769 Bug ID: 97769 Summary: [11 Regression] vectorizer ICE when building perlbench in SPECCPU 2017 Product: gcc Version: 11.0 Status: UNCONFIRMED Keywords: ice-on-va

[Bug c/97769] [11 Regression] vectorizer ICE when building perlbench in SPECCPU 2017

2020-11-09 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97769 --- Comment #1 from Tamar Christina --- This seems to go away if you initialize a in `int a`.

[Bug tree-optimization/97736] [9/10/11 Regression] switch codegen

2020-11-09 Thread ncm at cantrip dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97736 --- Comment #6 from ncm at cantrip dot org --- The referenced patch seems to have also deleted a fair bit of explanatory comment text, including a list of possible refinements for selected targets.

[Bug fortran/97768] [10/11 Regression] 32-bit f951 ICE on code from OpenMolcas

2020-11-09 Thread anlauf at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97768 anlauf at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug fortran/97768] [10/11 Regression] 32-bit f951 ICE on code from OpenMolcas

2020-11-09 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97768 --- Comment #6 from Jakub Jelinek --- I'd have thought doing it inside of if (ex->ts.u.cl && ex->ts.u.cl->length) conditional and testing for ex->ts.u.cl->length->expr_type instead. Plus for the CHARACTER case, it doesn't need to use buffer and c

[Bug c++/97762] [11 Regression] ICE: Segmentation fault (in warn_about_ambiguous_parse)

2020-11-09 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97762 --- Comment #4 from CVS Commits --- The master branch has been updated by Marek Polacek : https://gcc.gnu.org/g:3a5f8d745f8e26d973218b088788f22ad197ca67 commit r11-4850-g3a5f8d745f8e26d973218b088788f22ad197ca67 Author: Marek Polacek Date: Mo

[Bug c++/97762] [11 Regression] ICE: Segmentation fault (in warn_about_ambiguous_parse)

2020-11-09 Thread mpolacek at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97762 Marek Polacek changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug fortran/97768] [10/11 Regression] 32-bit f951 ICE on code from OpenMolcas

2020-11-09 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97768 --- Comment #7 from Jakub Jelinek --- Created attachment 49529 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49529&action=edit gcc11-pr97768.patch More complete (but still untested) patch.

[Bug fortran/97589] Segementation fault when allocating coarrays.

2020-11-09 Thread tkoenig at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97589 --- Comment #4 from Thomas Koenig --- (In reply to Thomas Koenig from comment #3) > Simplified test case: > > program main > type foo > real, allocatable, dimension(:) :: a[:] > end type foo > type (foo) :: x > sync all > allocate

[Bug fortran/97589] Segementation fault when allocating coarrays.

2020-11-09 Thread tkoenig at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97589 Thomas Koenig changed: What|Removed |Added Status|REOPENED|NEW --- Comment #5 from Thomas Koenig -

[Bug fortran/97589] Segementation fault when allocating coarrays.

2020-11-09 Thread tkoenig at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97589 Thomas Koenig changed: What|Removed |Added Status|NEW |WAITING --- Comment #6 from Thomas Koeni

[Bug c++/93907] [10 Regression] internal compiler error: in hashtab_chk_error, at hash-table.c:137

2020-11-09 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93907 --- Comment #7 from CVS Commits --- The master branch has been updated by Patrick Palka : https://gcc.gnu.org/g:71a8040716c1342547a19c25bd0203ac29258ef3 commit r11-4856-g71a8040716c1342547a19c25bd0203ac29258ef3 Author: Patrick Palka Date: Mo

[Bug libstdc++/97759] Could std::has_single_bit be faster?

2020-11-09 Thread gcc-bugs at marehr dot dialup.fu-berlin.de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97759 --- Comment #8 from gcc-bugs at marehr dot dialup.fu-berlin.de --- Created attachment 49531 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49531&action=edit has_single_bit_benchmark.cpp

[Bug libstdc++/97759] Could std::has_single_bit be faster?

2020-11-09 Thread gcc-bugs at marehr dot dialup.fu-berlin.de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97759 --- Comment #7 from gcc-bugs at marehr dot dialup.fu-berlin.de --- Created attachment 49530 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49530&action=edit CMakeLists.txt

[Bug libstdc++/97759] Could std::has_single_bit be faster?

2020-11-09 Thread gcc-bugs at marehr dot dialup.fu-berlin.de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97759 --- Comment #9 from gcc-bugs at marehr dot dialup.fu-berlin.de --- Thank you for so many responses (In reply to Thomas Koenig from comment #1) > Could you post the benchmark and the exact architecture where the arithmetic > version is faster? ``

[Bug c++/94404] [meta-bug] C++ core issues

2020-11-09 Thread mpolacek at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94404 Bug 94404 depends on bug 97453, which changed state. Bug 97453 Summary: Implement CWG issue 2303 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97453 What|Removed |Added ---

[Bug c++/97453] Implement CWG issue 2303

2020-11-09 Thread mpolacek at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97453 Marek Polacek changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug libstdc++/97759] Could std::has_single_bit be faster?

2020-11-09 Thread gcc-bugs at marehr dot dialup.fu-berlin.de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97759 --- Comment #10 from gcc-bugs at marehr dot dialup.fu-berlin.de --- And maybe a related question: I know that an arithmetic implementation might auto-vectorize, but would a popcount implementation do that too? Since AVX512_BITALG (https://softwa

[Bug tree-optimization/97567] [11 Regression] wrong code at -Os and above on x86_64-pc-linux-gnu

2020-11-09 Thread amacleod at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97567 --- Comment #7 from Andrew Macleod --- The original fix was incorrect. It papered over a problem by reducing opportunities it could find. Given if (c_2 || c_3) If the FALSE edge is taken, this is ! (c_2 || c_3) which is equivalent to !c_2 &

[Bug tree-optimization/97567] [11 Regression] wrong code at -Os and above on x86_64-pc-linux-gnu

2020-11-09 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97567 --- Comment #8 from CVS Commits --- The master branch has been updated by Andrew Macleod : https://gcc.gnu.org/g:7d26a337bfa1135d95caa3c213e82f2a97f18a01 commit r11-4862-g7d26a337bfa1135d95caa3c213e82f2a97f18a01 Author: Andrew MacLeod Date:

[Bug target/97770] New: Missing vectorization for vpopcnt

2020-11-09 Thread crazylht at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97770 Bug ID: 97770 Summary: Missing vectorization for vpopcnt Product: gcc Version: 11.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal Priority:

[Bug target/97770] Missing vectorization for vpopcnt

2020-11-09 Thread crazylht at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97770 --- Comment #1 from Hongtao.liu --- For target side, we need to add expander for popcountm2 with m vector mode

[Bug libstdc++/97759] Could std::has_single_bit be faster?

2020-11-09 Thread crazylht at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97759 --- Comment #11 from Hongtao.liu --- (In reply to gcc-bugs from comment #10) > And maybe a related question: > > I know that an arithmetic implementation might auto-vectorize, but would a > popcount implementation do that too? > > Since AVX512_

[Bug target/97770] [ICELAKE]Missing vectorization for vpopcnt

2020-11-09 Thread crazylht at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97770 --- Comment #2 from Hongtao.liu --- After adding expander, successfully vectorize the loop. --- diff --git a/gcc/config/i386/sse.md b/gcc/config/i386/sse.md index b153a87fb98..e8159997c40 100644 --- a/gcc/config/i386/sse.md +++ b/gcc/config/i386/

[Bug target/97770] [ICELAKE]Missing vectorization for vpopcnt

2020-11-09 Thread crazylht at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97770 --- Comment #3 from Hongtao.liu --- > But for vector byte/word/quadword, vectorizer still use vpopcntd, but not > vpopcnt{b,w,q}, missing corresponding ifn? We don't have __builtin_popcount{w,b}, but we have __builtin_popcountl. for testcase --

[Bug c++/97771] New: gcc/g++ failed to generate proper .init_array entries for local scope function, should create "axG", .init_array comdat

2020-11-09 Thread erstrauss at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97771 Bug ID: 97771 Summary: gcc/g++ failed to generate proper .init_array entries for local scope function, should create "axG", .init_array comdat Product: gcc Versio

[Bug other/97417] RISC-V Unnecessary andi instruction when loading volatile bool

2020-11-09 Thread admin at levyhsu dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97417 Levy changed: What|Removed |Added Attachment #49524|0 |1 is obsolete|

[Bug other/97417] RISC-V Unnecessary andi instruction when loading volatile bool

2020-11-09 Thread kito at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97417 --- Comment #25 from Kito Cheng --- Seem like you have add code to gcc/optabs.h and gcc/optabs.c, however those functions are RISC-V specific, so I would suggest you put in riscv.c and riscv-protos.h.

[Bug other/97417] RISC-V Unnecessary andi instruction when loading volatile bool

2020-11-09 Thread admin at levyhsu dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97417 Levy changed: What|Removed |Added Attachment #49532|0 |1 is obsolete|

[Bug other/97417] RISC-V Unnecessary andi instruction when loading volatile bool

2020-11-09 Thread admin at levyhsu dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97417 --- Comment #27 from Levy --- (In reply to Kito Cheng from comment #25) > Seem like you have add code to gcc/optabs.h and gcc/optabs.c, however those > functions are RISC-V specific, so I would suggest you put in riscv.c and > riscv-protos.h. No

[Bug other/97417] RISC-V Unnecessary andi instruction when loading volatile bool

2020-11-09 Thread admin at levyhsu dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97417 Levy changed: What|Removed |Added Attachment #49533|0 |1 is obsolete|

[Bug c++/97772] New: Wording of GCC's error message when calling lvalue-ref qualified member function on temporary object

2020-11-09 Thread enricomaria.dean6elis at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97772 Bug ID: 97772 Summary: Wording of GCC's error message when calling lvalue-ref qualified member function on temporary object Product: gcc Version: 10.2.0 Status: UNCONFIRM

<    1   2