https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79856
Roland Illig changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79856
Martin Liška changed:
What|Removed |Added
Assignee|marxin at gcc dot gnu.org |unassigned at gcc dot
gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79856
--- Comment #8 from Roland Illig ---
(In reply to Martin Liška from comment #7)
> I like your rules. My question was more about how practically do you
> distinguish between such strings? My plan is to create a new
> DK_INTERNAL_ERROR type, which
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79856
--- Comment #7 from Martin Liška ---
(In reply to Roland Illig from comment #6)
> I would define the rules as follows, the first matching rule wins:
>
> 1. do not translate messages that contain names of GCC implementation
> functions
>
> 2. do
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79856
--- Comment #6 from Roland Illig ---
I would define the rules as follows, the first matching rule wins:
1. do not translate messages that contain names of GCC implementation functions
2. do not translate messages that contain the words GIMPLE,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79856
--- Comment #5 from Martin Liška ---
Created attachment 40958
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40958&action=edit
Candidate untested patch
I'm sending candidate patch. Can you please Roland tell me where we distinguish
which m
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79856
--- Comment #4 from Roland Illig ---
(In reply to Richard Biener from comment #3)
> So maybe we instead want a internal_error_cont () which will not end
> compilation.
I would be very happy with that.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79856
--- Comment #3 from Richard Biener ---
So maybe we instead want a internal_error_cont () which will not end
compilation.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79856
--- Comment #2 from Richard Biener ---
Note that internal_error will terminate GCC immediately while error () allows
for further errors to be diagnosed. Which is what we want here, internal_error
is done as the final step in "CFG verification fa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79856
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
10 matches
Mail list logo
