> On Jul 2, 2024, at 18:02, David Malcolm wrote:
>
> On Tue, 2024-07-02 at 16:17 +, Qing Zhao wrote:
>> due to code duplication from jump threading [PR109071]
>> Control this with a new option -fdiagnostic-try-to-explain-harder.
>
> The name -fdiagnostic-try-to-explain-harder seems a littl
On Tue, 2024-07-02 at 18:02 -0400, David Malcolm wrote:
> On Tue, 2024-07-02 at 16:17 +, Qing Zhao wrote:
[...snip...]
>
> > + path.add_event (cur_ch->condition, NULL_TREE, 0,
> > + "when the condition is evaluated to %s",
> > + cur_ch->is_true_path ? "t
On Tue, 2024-07-02 at 16:17 +, Qing Zhao wrote:
> due to code duplication from jump threading [PR109071]
> Control this with a new option -fdiagnostic-try-to-explain-harder.
The name -fdiagnostic-try-to-explain-harder seems a little too "cute"
to me, but I can't think of a better name.
Variou
due to code duplication from jump threading [PR109071]
Control this with a new option -fdiagnostic-try-to-explain-harder.
This patch has been tested with -fdiagnostic-try-to-expain-harder on by
default to bootstrap gcc and regression testing on both x86 and aarch64,
resolved all bootstrap issues a
