https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80012
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80012
--- Comment #8 from Roland Illig ---
(In reply to Jakub Jelinek from comment #7)
> (In reply to Jerry DeLisle from comment #5)
> > Another way is to build an error message with snprintf for example and use
> > that string in the error message.
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80012
--- Comment #7 from Jakub Jelinek ---
(In reply to Jerry DeLisle from comment #5)
> Another way is to build an error message with snprintf for example and use
> that string in the error message.
That is translation unfriendly.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80012
--- Comment #6 from Jakub Jelinek ---
At least in the middle-end or C/C++ FEs such diagnostics is done with
error{,_at}/warning{,_at} etc. followed by inform, for warning inform only
called if warning* returned true, and wrapped with auto_diagnos
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80012
Jerry DeLisle changed:
What|Removed |Added
CC||jvdelisle at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80012
Anuj Mohite changed:
What|Removed |Added
CC||anujmohite001 at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80012
Eric Gallager changed:
What|Removed |Added
Keywords||diagnostic, easyhack, FIXME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80012
Dominique d'Humieres changed:
What|Removed |Added
Priority|P3 |P4
See Also|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80012
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80012
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80012
Manuel López-Ibáñez changed:
What|Removed |Added
CC||manu at gcc dot gnu.org
--- Commen
11 matches
Mail list logo