On 13/01/2020 10:40, Matthew Malcomson wrote:
On 11/01/2020 07:19, Gerald Pfeifer wrote:
On Thu, 12 Dec 2019, Matthew Malcomson wrote:
gcc/ChangeLog:
2019-12-12 Matthew Malcomson <matthew.malcom...@arm.com>
* doc/install.texi: Document bootstrap-asan configuration option.
I see this introduces a new table.
+Some examples of build configurations designed for developers of GCC are:
@samp{bootstrap-time}, @samp{bootstrap-debug-ckovw} and others appear
to fall into the same camp, essentially expected to be used by maintainers
only.
Would it make sense to add your new option to the existing table, or
perhaps see which other options from the existing table to move into
your new one? Thoughts?
Sounds good me.
The patch is okay modulo the question above.
Hi,
Apologies for bringing up something from this far back, but I've just
noticed I never actually committed this patch.
Did the above line mean approval once the option was moved into the
existing table? Or was it just explaining that the position was the
only problem you saw?
In other words: is the patch I proposed below Ok for trunk?
Thanks,
Matthew
Thanks,
Gerald
Patch with above suggestion.
#####################
diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index
80b47812fe66a8ef50edf3aad9708ab3409ba7dc..0705759c69f64c6d06e91f7ae83bb8c1ad210f34
100644
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -2668,6 +2668,10 @@ Arranges for the run time of each program started
by the GCC driver,
built in any stage, to be logged to @file{time.log}, in the top level of
the build tree.
+@item @samp{bootstrap-asan}
+Compiles GCC itself using Address Sanitization in order to catch
invalid memory
+accesses within the GCC code.
+
@end table
@section Building a cross compiler
