This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug rtl-optimization/79856] rtl_verify_edges: use internal_error instead of error
- From: "roland.illig at gmx dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 15 Mar 2017 17:49:51 +0000
- Subject: [Bug rtl-optimization/79856] rtl_verify_edges: use internal_error instead of error
- Auto-submitted: auto-generated
- References: <bug-79856-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79856
--- Comment #8 from Roland Illig <roland.illig at gmx dot de> ---
(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 I would like to ignore in the translations.
I don't know what you mean by "distinguish". As I suggested in
https://gcc.gnu.org/ml/gcc/2017-03/msg00049.html, I would solve this by having
two separate functions for errors: error() and error_no_i18n().
Can you elaborate a bit on what you meant?