https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115007
porten at kde dot org changed:
What|Removed |Added
CC||porten at kde dot org
++
Assignee: unassigned at gcc dot gnu.org
Reporter: porten at kde dot org
Target Milestone: ---
Purely by accident, I ran into an ICE when using -ftime-report on a file
including a system header with a .gcm file of that header present. The scenario
appeared after an attempt to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114795
--- Comment #10 from porten at kde dot org ---
It is! Even my original code base now fully compiles without errors. Thank you!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114795
--- Comment #6 from porten at kde dot org ---
The test case for the other ICE is quite similar to the first one:
- command
g++ -std=c++2a -fmodules-ts -c url.cpp queue.cpp
--- url.cp ---
module
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114795
--- Comment #4 from porten at kde dot org ---
Thanks for the reminder about the workaround. I had once seen it before trying
module but did not see the relation when running into problems later. In the
small test case, reordering the import and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114795
--- Comment #2 from porten at kde dot org ---
The ICE is still there with current master
(f17d31e709af9b2d488adecd6cd040dfc1f23b04). The test case provided in bug
#114600 works for me now, though. So similar but seemingly no duplicate after
all.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114795
--- Comment #1 from porten at kde dot org ---
Looking through the other c++-modules reports, I saw that someone reduced a
similar test case to an ICE in comment #3:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114600#c3 Therefore this bug
could
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: porten at kde dot org
Target Milestone: ---
This is with a gcc/g++ build created locally from the published snapshot
package gcc-14-20240414.tar.xz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67551
--- Comment #4 from porten at kde dot org ---
Right. Usage of #line would be nicer. But if the additional bytes just slow
down things...
The recommended -fpreprocessed appears to be a good workaround. Does it maybe
even speed up the compilation?
: preprocessor
Assignee: unassigned at gcc dot gnu.org
Reporter: porten at kde dot org
Target Milestone: ---
The code emitted by the preprocessor does produce warnings when compiled as
C/C++ code with -pedantic:
$ echo "int main() { return 0; }" > input.c
$ cp
--- Additional Comments From porten at kde dot org 2004-12-21 07:14 ---
Re comment #8: my report #18018 was actually in relation to exactly this file
from the Qt package. The test case is a destilled version.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16792
P2
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: porten at kde dot org
CC: gcc-bugs at gcc dot gnu dot org
GCC host triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18018
12 matches
Mail list logo
