[Bug c/94990] New: NFC / NFD in identifiers

: unassigned at gcc dot gnu.org Reporter: Arfrever.FTA at GMail dot Com Target Milestone: --- GCC 10 introduced support for non-ASCII characters in identifiers. However it is incomplete in context of NFC / NFD [1]: $ gcc -o /tmp/test -x c - <<<"int ś = 123; int main() {ret

[Bug target/85915] New: -mfunction-return=thunk causes multiple definition of `__x86_return_thunk'

erity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: Arfrever.FTA at GMail dot Com CC: hjl.tools at gmail dot com Target Milestone: --- This is a regression in GCC 8.1.0. $ gcc-7.3.0 -mfunction-return=

[Bug web/85916] New: GCC 8 Changes page has outdated mention of -mibt, -mcet and maybe -mshstk

/changes.html Status: UNCONFIRMED Severity: normal Priority: P3 Component: web Assignee: unassigned at gcc dot gnu.org Reporter: Arfrever.FTA at GMail dot Com CC: hjl.tools at gmail dot com Target Milestone: --- https://gcc.gnu.org

[Bug web/85917] New: GCC 8 Changes page fails to mention change of default mode for C

Status: UNCONFIRMED Severity: normal Priority: P3 Component: web Assignee: unassigned at gcc dot gnu.org Reporter: Arfrever.FTA at GMail dot Com Target Milestone: --- GCC 8 changed default mode for C from -std=gnu11 to -std=gnu17, but https

[Bug web/85916] GCC 8 Changes page has outdated mention of -mibt, -mcet and maybe -mshstk

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85916 --- Comment #2 from Arfrever Frehtes Taifersar Arahesis --- A space is missing between "-fcf-protection" and "option" in this sentence: """ GCC now supports the Intel Control-flow Enforcement Technology (CET) extension through -fcf-protectionopti

[Bug other/85928] New: Misplaced references to some options in info page in Option Index

Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: Arfrever.FTA at GMail dot Com Target Milestone: --- `info gcc "Option Index"` opens "Option Index" page, which cont

[Bug target/85915] -mfunction-return=thunk causes multiple definition of `__x86_return_thunk'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85915 --- Comment #2 from Arfrever Frehtes Taifersar Arahesis --- I have firstly rebuilt glibc with GCC 8.1.0 without -mfunction-return=thunk and at that time GCC 7.3.0 and 8.1.0 were working. Next I have rebuilt glibc with GCC 8.1.0 with -mfunction-r

[Bug target/85915] -mfunction-return=thunk causes multiple definition of `__x86_return_thunk'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85915 --- Comment #3 from Arfrever Frehtes Taifersar Arahesis --- If you claim that it is a bug in GCC 7.3.0, then please try to fix it in GCC 7.4.0, preferably without breaking ABI compatilibity...

[Bug target/85915] -mfunction-return=thunk causes multiple definition of `__x86_return_thunk'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85915 --- Comment #5 from Arfrever Frehtes Taifersar Arahesis --- Do you know numbers of relevant revisions which I could locally backport to GCC 7.3.0?

[Bug target/85915] -mfunction-return=thunk causes multiple definition of `__x86_return_thunk'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85915 --- Comment #7 from Arfrever Frehtes Taifersar Arahesis --- Ebuild for GCC 7 branch is not available in Gentoo. I guess that the relevant commit is: https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=258647 https://gcc.gnu.org/git/?p=gcc.git;

[Bug web/85917] GCC 8 Changes page fails to mention change of default mode for C

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85917 --- Comment #2 from Arfrever Frehtes Taifersar Arahesis --- Even such minor changes could be mentioned in that page for completeness.

[Bug target/85915] ABI incompatibility (multiple definition of `__x86_return_thunk') for static libraries, between GCC 7.3.0 and GCC >=7.4.0, caused by -mfunction-return=thunk

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85915 Arfrever Frehtes Taifersar Arahesis changed: What|Removed |Added Summary|ABI incompatibility |ABI incompatibility

[Bug driver/83243] -fuse-ld=lld

GMail dot Com --- Comment #7 from Arfrever Frehtes Taifersar Arahesis --- (In reply to H.J. Lu from comment #5) > commit 4eea76dbfc871614e116961b048d9aa38eee66ea > Author: law > Date: Thu Nov 8 22:05:27 2018 + > > * collect2.c (linker_select):

[Bug java/61552] New: Unneeded check for libart

Assignee: unassigned at gcc dot gnu.org Reporter: Arfrever.FTA at GMail dot Com According to my grepping, libart was actually used only in GCC 3.4.* and 4.0.* (e.g. libart headers were included in GCC's libjava/jni/gtk-peer/gnu_java_awt_peer_gtk_GtkImagePainter.c). libjava/configure.ac i

[Bug java/61552] Unneeded check for libart

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61552 --- Comment #1 from Arfrever Frehtes Taifersar Arahesis --- Created attachment 33974 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33974&action=edit gcc_delete_libart_check.patch

[Bug c++/99375] New: Segmentation fault in code compiled with -O1 -ftree-loop-vectorize

Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: Arfrever.FTA at GMail dot Com Target Milestone: --- For MARISA project (https://github.com/s-yata/marisa-trie), GCC 10.2.0 with at least CXXFLAGS="-O1 -ftree-loop-vectorize"

[Bug c++/99375] Segmentation fault in code compiled with -O1 -ftree-loop-vectorize

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99375 --- Comment #2 from Arfrever Frehtes Taifersar Arahesis --- I confirm that backporting of GCC commit 1ab88985631dd2c5a5e3b5c0dce47cf8b6ed2f82 (https://gcc.gnu.org/g:1ab88985631dd2c5a5e3b5c0dce47cf8b6ed2f82) to GCC 10.2.0 fixes this problem (also