Non-consistent ICE in 14.1 and 14.2
Hi GCC I wanted to report one or more bugs, unfortunately they are not consistently reproducable, which is odd. It happens when compiling the chromium part of qtwebengine after the update to gcc 14 and during development for updating Chromium to 126. On almost every run over a few thousand files one or more files will crash with an ICE, that goes away if you just build again. I was under the impression gcc was doing everything reproducable, so this is really confusing. The errors claim different random spots in the sources with either "internal compiler error: Segmentation fault" or "internal compiler error: in tree_node_structure_for_code, at tree:527" How should I approach reporting this to get it fixed? Best regards Allan
Re: Non-consistent ICE in 14.1 and 14.2
On Thu, Aug 29, 2024 at 1:49 PM Allan Sandfeld Jensen wrote: > > Hi GCC > > I wanted to report one or more bugs, unfortunately they are not consistently > reproducable, which is odd. It happens when compiling the chromium part of > qtwebengine after the update to gcc 14 and during development for updating > Chromium to 126. On almost every run over a few thousand files one or more > files will crash with an ICE, that goes away if you just build again. I was > under the impression gcc was doing everything reproducable, so this is really > confusing. > > The errors claim different random spots in the sources with either "internal > compiler error: Segmentation fault" or "internal compiler error: in > tree_node_structure_for_code, at tree:527" > > How should I approach reporting this to get it fixed? It sounds you might got faulty memory in your system. Richard. > > Best regards > Allan > >
Re: Non-consistent ICE in 14.1 and 14.2
On Thu, 29 Aug 2024, Richard Biener via Gcc wrote: > On Thu, Aug 29, 2024 at 1:49 PM Allan Sandfeld Jensen > wrote: > > > > Hi GCC > > > > I wanted to report one or more bugs, unfortunately they are not consistently > > reproducable, which is odd. It happens when compiling the chromium part of > > qtwebengine after the update to gcc 14 and during development for updating > > Chromium to 126. On almost every run over a few thousand files one or more > > files will crash with an ICE, that goes away if you just build again. I was > > under the impression gcc was doing everything reproducable, so this is > > really > > confusing. > > > > The errors claim different random spots in the sources with either "internal > > compiler error: Segmentation fault" or "internal compiler error: in > > tree_node_structure_for_code, at tree:527" > > > > How should I approach reporting this to get it fixed? > > It sounds you might got faulty memory in your system. Allan, what CPU is that on? If Intel 13th or 14th gen, that's not entirely unexpected, unfortunately, due to voltage management issues (or manufacturing, on some earlier samples). Alexander
Re: Non-consistent ICE in 14.1 and 14.2
On Thursday 29 August 2024 14:38:04 Central European Summer Time Alexander Monakov wrote: > On Thu, 29 Aug 2024, Richard Biener via Gcc wrote: > > On Thu, Aug 29, 2024 at 1:49 PM Allan Sandfeld Jensen > > > > wrote: > > > Hi GCC > > > > > > I wanted to report one or more bugs, unfortunately they are not > > > consistently reproducable, which is odd. It happens when compiling the > > > chromium part of qtwebengine after the update to gcc 14 and during > > > development for updating Chromium to 126. On almost every run over a > > > few thousand files one or more files will crash with an ICE, that goes > > > away if you just build again. I was under the impression gcc was doing > > > everything reproducable, so this is really confusing. > > > > > > The errors claim different random spots in the sources with either > > > "internal compiler error: Segmentation fault" or "internal compiler > > > error: in tree_node_structure_for_code, at tree:527" > > > > > > How should I approach reporting this to get it fixed? > > > > It sounds you might got faulty memory in your system. > > Allan, what CPU is that on? If Intel 13th or 14th gen, that's not entirely > unexpected, unfortunately, due to voltage management issues (or > manufacturing, on some earlier samples). > It is an AMD Ryzen 9 5950X, so not one that is built to fail.. I will check for hardware flaws anyway though, and report back if this happens on different hardware. Best regards Allan
History/Pupose of Double Newline in gcc --version
Hi, I noticed gcc --version produces two newlines at the end of the version message. See below. -- $ gcc --version gcc (GCC) 12.4.0 Copyright (C) 2022 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. $ [next shell line here] -- I see in files like gcc/gcc.cc and gcc/gcov.cc the string with two newlines is intentionally used: "This is free software; see the source for copying conditions. There is NO\n\ warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.\n\n" I was curious if there was some historical reason for the "\n\n". Ryder
gcc-12-20240829 is now available
Snapshot gcc-12-20240829 is now available on https://gcc.gnu.org/pub/gcc/snapshots/12-20240829/ and on various mirrors, see https://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 12 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch releases/gcc-12 revision 9742dbd709ff316aebc72b35b8c63c51d763d42b You'll find: gcc-12-20240829.tar.xz Complete GCC SHA256=38cdcd557916ae9b3fb09cd33703190ec717c85ed42c11a8bd6a5c14cd7db341 SHA1=17003cc5607de9ca6d67446fa919e52f4b28ce95 Diffs from 12-20240822 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-12 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
