https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85777
--- Comment #10 from Vincent Lefèvre ---
(In reply to Jakub Jelinek from comment #9)
> That is not true, automake is highly customizable, you can e.g. override
> COMPILE/LTCOMPILE variables in Makefile.am or something similar.
The issue is that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85777
--- Comment #9 from Jakub Jelinek ---
That is not true, automake is highly customizable, you can e.g. override
COMPILE/LTCOMPILE variables in Makefile.am or something similar.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85777
--- Comment #8 from Vincent Lefèvre ---
(In reply to Eric Gallager from comment #7)
> you can still add handwritten rules in Automake Makefiles to be used
> alongside the Automake-generated rules.
But if the goal is to replace the compilation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85777
--- Comment #7 from Eric Gallager ---
(In reply to Vincent Lefèvre from comment #6)
> But this cannot apply to projects that use GNU Automake, which does not
> generate such rules. And with Automake, things are more complex in practice,
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85777
--- Comment #6 from Vincent Lefèvre ---
But this cannot apply to projects that use GNU Automake, which does not
generate such rules. And with Automake, things are more complex in practice,
because in the rules, there are additional options for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85777
--- Comment #5 from Jakub Jelinek ---
That can be dealt in the Makefile rules, for sanitization use something like
$(CC) $(CFLAGS) $(WARNOPTS) -S -o /dev/null $<
$(CC) $(CFLAGS) $(SANITIZEOPTS) -c -o $@ $< 2>/dev/null
or similar.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85777
--- Comment #4 from Vincent Lefèvre ---
(In reply to Jakub Jelinek from comment #3)
> If you care about warnings as well as sanitization, I'd suggest separate
> builds for warnings and for sanitization, the latter perhaps with -w.
This is fine
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85777
--- Comment #3 from Jakub Jelinek ---
The expectations that sanitization doesn't change generated warnings is a wrong
one, the runtime instrumentation affects the code generation so much that
necessarily some further warnings will be emitted and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85777
Richard Biener changed:
What|Removed |Added
Target Milestone|7.4 |7.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85777
Richard Biener changed:
What|Removed |Added
Keywords||diagnostic
Priority|P3
10 matches
Mail list logo
