[Bug c++/109936] error: extended character ≠ is not valid in an identifier

2023-05-23 Thread adam at wozniakconsulting dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109936 --- Comment #26 from Adam Wozniak --- (In reply to Jonathan Wakely from comment #19) > (In reply to Andreas Schwab from comment #10) > > It is a valid preprocessing token ("non-whitespace character that cannot be > > one of the above"). > > Ah

[Bug c++/109936] error: extended character ≠ is not valid in an identifier

2023-05-23 Thread adam at wozniakconsulting dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109936 --- Comment #24 from Adam Wozniak --- (In reply to Jonathan Wakely from comment #23) > (In reply to Adam Wozniak from comment #20) > > i get this response: > > > > This page contains the following errors: > > error on line 20 at column 54: AttV

[Bug c++/109936] error: extended character ≠ is not valid in an identifier

2023-05-23 Thread adam at wozniakconsulting dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109936 --- Comment #22 from Adam Wozniak --- (In reply to Jonathan Wakely from comment #19) > (In reply to Andreas Schwab from comment #10) > > It is a valid preprocessing token ("non-whitespace character that cannot be > > one of the above"). > > Ah

[Bug c++/109936] error: extended character ≠ is not valid in an identifier

2023-05-23 Thread adam at wozniakconsulting dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109936 --- Comment #21 from Adam Wozniak --- (In reply to Andrew Pinski from comment #16) > It is funny arguing with folks who write parts of GCC on an idea of > integrated vs seperate preprocessor really. yeah, i've been pounding out C since the late

[Bug c++/109936] error: extended character ≠ is not valid in an identifier

2023-05-23 Thread adam at wozniakconsulting dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109936 --- Comment #20 from Adam Wozniak --- (In reply to Andrew Pinski from comment #17) > (In reply to Adam Wozniak from comment #13) > > (In reply to Jakub Jelinek from comment #11) > > > Bisection points to r10-3309-g7d112d6670a0e0e662 > > > > tha

[Bug c++/109936] error: extended character ≠ is not valid in an identifier

2023-05-22 Thread adam at wozniakconsulting dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109936 --- Comment #15 from Adam Wozniak --- (In reply to Jonathan Wakely from comment #6) > ≠ cannot be used in an identifier, and it's none of the other forms either. at the risk of beating a dead horse, what you are saying here is that ≠ simply can

[Bug c++/109936] error: extended character ≠ is not valid in an identifier

2023-05-22 Thread adam at wozniakconsulting dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109936 --- Comment #14 from Adam Wozniak --- (In reply to Adam Wozniak from comment #12) > (In reply to Jonathan Wakely from comment #9) > > (In reply to Adam Wozniak from comment #8) > > > i don't think of the preprocessor as part of the compiler. > >

[Bug c++/109936] error: extended character ≠ is not valid in an identifier

2023-05-22 Thread adam at wozniakconsulting dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109936 --- Comment #13 from Adam Wozniak --- (In reply to Jakub Jelinek from comment #11) > Bisection points to r10-3309-g7d112d6670a0e0e662 that link gives me an error

[Bug c++/109936] error: extended character ≠ is not valid in an identifier

2023-05-22 Thread adam at wozniakconsulting dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109936 --- Comment #12 from Adam Wozniak --- (In reply to Jonathan Wakely from comment #9) > (In reply to Adam Wozniak from comment #8) > > i don't think of the preprocessor as part of the compiler. > > it's a different step, a different executable, th

[Bug c++/109936] error: extended character ≠ is not valid in an identifier

2023-05-22 Thread adam at wozniakconsulting dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109936 --- Comment #8 from Adam Wozniak --- (In reply to Jonathan Wakely from comment #6) > That isn't the point. The compiler has to tokenize the input in order to > perform the preprocessing step. That means it has to be able to decide what > the byt

[Bug c++/109936] error: extended character ≠ is not valid in an identifier

2023-05-22 Thread adam at wozniakconsulting dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109936 Adam Wozniak changed: What|Removed |Added Resolution|INVALID |--- Status|RESOLVED

[Bug c++/109936] New: error: extended character ≠ is not valid in an identifier

2023-05-22 Thread adam at wozniakconsulting dot com via Gcc-bugs
Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: adam at wozniakconsulting dot com Target Milestone: --- Created attachment 55138 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55138&action=edit cpp file that demonstra

[Bug c/59126] New: internal compiler error: Segmentation fault

2013-11-13 Thread adam at wozniakconsulting dot com
Assignee: unassigned at gcc dot gnu.org Reporter: adam at wozniakconsulting dot com Created attachment 31214 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31214&action=edit preprocessed source $ lsb_release -a LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.