Message ID | 20230721190234.1018000-1-qing.zhao@oracle.com |
---|---|
State | New |
Headers | show |
Series | gcc-13/changes.html: Add and fix URL to -fstrict-flex-array option. | expand |
Ping. This is a very simple patch to correct a URL address in GCC13’s changes.html. Currently, it’s pointing to a wrong address. Okay for committing? > On Jul 21, 2023, at 3:02 PM, Qing Zhao <qing.zhao@oracle.com> wrote: > > Hi, > > In the current GCC13 release note, the URL to the option -fstrict-flex-array > is wrong (pointing to -Wstrict-flex-array). > This is the change to correct the URL and also add the URL in another place > where -fstrict-flex-array is mentioned. > > I have checked the resulting HTML file, works well. > > Okay for committing? > > thanks. > > Qing > --- > htdocs/gcc-13/changes.html | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html > index 68e8c5cc..39b63a84 100644 > --- a/htdocs/gcc-13/changes.html > +++ b/htdocs/gcc-13/changes.html > @@ -46,7 +46,7 @@ You may also want to check out our > will no longer issue warnings for out of > bounds accesses to trailing struct members of one-element array type > anymore. Instead it diagnoses accesses to trailing arrays according to > - <code>-fstrict-flex-arrays</code>. </li> > + <a href="https://gcc.gnu.org/onlinedocs/gcc-13.1.0/gcc/C-Dialect-Options.html#index-fstrict-flex-arrays"><code>-fstrict-flex-arrays</code></a>. </li> > <li><a href="https://gcc.gnu.org/onlinedocs/gcc-13.1.0/gcc/Static-Analyzer-Options.html"><code>-fanalyzer</code></a> > is still only suitable for analyzing C code. > In particular, using it on C++ is unlikely to give meaningful output.</li> > @@ -213,7 +213,7 @@ You may also want to check out our > flexible array member for the purpose of accessing the elements of such > an array. By default, all trailing arrays in aggregates are treated as > flexible array members. Use the new command-line option > - <a href="https://gcc.gnu.org/onlinedocs/gcc-13.1.0/gcc/Warning-Options.html#index-Wstrict-flex-arrays"><code>-fstrict-flex-arrays</code></a> > + <a href="https://gcc.gnu.org/onlinedocs/gcc-13.1.0/gcc/C-Dialect-Options.html#index-fstrict-flex-arrays"><code>-fstrict-flex-arrays</code></a> > to control which array members are treated as flexible arrays. > </li> > </ul> > -- > 2.31.1 >
On Wed, 2 Aug 2023, Qing Zhao wrote: > Ping. > > This is a very simple patch to correct a URL address in GCC13?s changes.html. > Currently, it?s pointing to a wrong address. > > Okay for committing? OK > > On Jul 21, 2023, at 3:02 PM, Qing Zhao <qing.zhao@oracle.com> wrote: > > > > Hi, > > > > In the current GCC13 release note, the URL to the option -fstrict-flex-array > > is wrong (pointing to -Wstrict-flex-array). > > This is the change to correct the URL and also add the URL in another place > > where -fstrict-flex-array is mentioned. > > > > I have checked the resulting HTML file, works well. > > > > Okay for committing? > > > > thanks. > > > > Qing > > --- > > htdocs/gcc-13/changes.html | 4 ++-- > > 1 file changed, 2 insertions(+), 2 deletions(-) > > > > diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html > > index 68e8c5cc..39b63a84 100644 > > --- a/htdocs/gcc-13/changes.html > > +++ b/htdocs/gcc-13/changes.html > > @@ -46,7 +46,7 @@ You may also want to check out our > > will no longer issue warnings for out of > > bounds accesses to trailing struct members of one-element array type > > anymore. Instead it diagnoses accesses to trailing arrays according to > > - <code>-fstrict-flex-arrays</code>. </li> > > + <a href="https://gcc.gnu.org/onlinedocs/gcc-13.1.0/gcc/C-Dialect-Options.html#index-fstrict-flex-arrays"><code>-fstrict-flex-arrays</code></a>. </li> > > <li><a href="https://gcc.gnu.org/onlinedocs/gcc-13.1.0/gcc/Static-Analyzer-Options.html"><code>-fanalyzer</code></a> > > is still only suitable for analyzing C code. > > In particular, using it on C++ is unlikely to give meaningful output.</li> > > @@ -213,7 +213,7 @@ You may also want to check out our > > flexible array member for the purpose of accessing the elements of such > > an array. By default, all trailing arrays in aggregates are treated as > > flexible array members. Use the new command-line option > > - <a href="https://gcc.gnu.org/onlinedocs/gcc-13.1.0/gcc/Warning-Options.html#index-Wstrict-flex-arrays"><code>-fstrict-flex-arrays</code></a> > > + <a href="https://gcc.gnu.org/onlinedocs/gcc-13.1.0/gcc/C-Dialect-Options.html#index-fstrict-flex-arrays"><code>-fstrict-flex-arrays</code></a> > > to control which array members are treated as flexible arrays. > > </li> > > </ul> > > -- > > 2.31.1 > > > >
diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html index 68e8c5cc..39b63a84 100644 --- a/htdocs/gcc-13/changes.html +++ b/htdocs/gcc-13/changes.html @@ -46,7 +46,7 @@ You may also want to check out our will no longer issue warnings for out of bounds accesses to trailing struct members of one-element array type anymore. Instead it diagnoses accesses to trailing arrays according to - <code>-fstrict-flex-arrays</code>. </li> + <a href="https://gcc.gnu.org/onlinedocs/gcc-13.1.0/gcc/C-Dialect-Options.html#index-fstrict-flex-arrays"><code>-fstrict-flex-arrays</code></a>. </li> <li><a href="https://gcc.gnu.org/onlinedocs/gcc-13.1.0/gcc/Static-Analyzer-Options.html"><code>-fanalyzer</code></a> is still only suitable for analyzing C code. In particular, using it on C++ is unlikely to give meaningful output.</li> @@ -213,7 +213,7 @@ You may also want to check out our flexible array member for the purpose of accessing the elements of such an array. By default, all trailing arrays in aggregates are treated as flexible array members. Use the new command-line option - <a href="https://gcc.gnu.org/onlinedocs/gcc-13.1.0/gcc/Warning-Options.html#index-Wstrict-flex-arrays"><code>-fstrict-flex-arrays</code></a> + <a href="https://gcc.gnu.org/onlinedocs/gcc-13.1.0/gcc/C-Dialect-Options.html#index-fstrict-flex-arrays"><code>-fstrict-flex-arrays</code></a> to control which array members are treated as flexible arrays. </li> </ul>