https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103626
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103626
--- Comment #12 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:7cc9022f8d5c5cc02cc4f8af2f27184a81536fcf
commit r13-3043-g7cc9022f8d5c5cc02cc4f8af2f27184a81536fcf
Author: Arsen ArsenoviÄ
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103626
--- Comment #9 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:46eb2860942a29b40822570cb6625620f69ed30e
commit r13-3039-g46eb2860942a29b40822570cb6625620f69ed30e
Author: Arsen ArsenoviÄ
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103626
--- Comment #10 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:25ebfdb774c0e8cc6c55e02644ee2cb157ce29d7
commit r13-3040-g25ebfdb774c0e8cc6c55e02644ee2cb157ce29d7
Author: Jonathan Wakely
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103626
--- Comment #10 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:25ebfdb774c0e8cc6c55e02644ee2cb157ce29d7
commit r13-3040-g25ebfdb774c0e8cc6c55e02644ee2cb157ce29d7
Author: Jonathan Wakely
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103626
--- Comment #8 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:18f176d0b25591e2880bc5ef453ce0834f9e0e2a
commit r13-3037-g18f176d0b25591e2880bc5ef453ce0834f9e0e2a
Author: Arsen ArsenoviÄ
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103626
--- Comment #7 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:f1b51f68f8ac6c63e352dda8599aed01634212de
commit r13-3034-gf1b51f68f8ac6c63e352dda8599aed01634212de
Author: Jonathan Wakely
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103626
--- Comment #6 from Arsen Arsenović ---
Agreed. Now that I think about it, it'd be just as easy to spot errors if
something in freestanding is relying on a hosted feature by just trying to
#include those headers on a freestanding install, so
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103626
--- Comment #5 from Jonathan Wakely ---
If a header doesn't depend on any of , etc and could work for
freestanding, do we want to explicitly disable out with #error, or make it
available as an extension?
Since the direction in the standard is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103626
--- Comment #4 from Arsen Arsenović ---
(In reply to Jonathan Wakely from comment #3)
> I don't think we need to add the #error to every header. For a start, users
> never include the bits/* headers directly, and if they do, it's their
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103626
--- Comment #3 from Jonathan Wakely ---
I don't think we need to add the #error to every header. For a start, users
never include the bits/* headers directly, and if they do, it's their problem.
So we only need to mark the standard headers as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103626
--- Comment #2 from Arsen Arsenović ---
I started work on marking headers, and I already marked 162 headers (all of
include/{std,bits,backward}, where appropriate) as part of my work on P1642.
This set also lines up with the set of all
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103626
Jonathan Wakely changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
13 matches
Mail list logo
