public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marek Polacek <polacek@redhat.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [wwwdocs] Update changes.html
Date: Mon, 11 May 2015 16:17:00 -0000	[thread overview]
Message-ID: <20150511161653.GR3384@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.20.1505111800270.2736@tuna.site>

On Mon, May 11, 2015 at 06:04:48PM +0200, Gerald Pfeifer wrote:
> Hi Marek,
> 
> On Mon, 11 May 2015, Marek Polacek wrote:
> > Ok to commit?
> 
> as maintainer I am happy for you to commit documentation/web changes
> without approval, though I am also happy to review.

I was hoping you could glance over it before I commit the patch; and
given the below, I'm glad you did ;).
 
> Here I'm wondering whether the nested list could just be merged
> into the primary item (and I'd omit the colon before "enables").

Agreed.  If we have more new options, we can make a list out of it.
 
> "a union".  English can be tricky for us non-native speakers at 
> times, since usually you would use "an" before "u", except when 
> that "u" is pronounced as a consonant or a syllable starting with 
> one.  And the "u" in "union" actually is prounced as "you-nion".

Yeah, I'm familiar with this rule, and I usually got that right.
Not sure how I goofed it up this time.

Is the following any better?  Thanks,

Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-6/changes.html,v
retrieving revision 1.3
diff -u -r1.3 changes.html
--- changes.html	6 May 2015 09:55:29 -0000	1.3
+++ changes.html	11 May 2015 16:16:04 -0000
@@ -16,15 +16,34 @@
 
 
 <!-- .................................................................. -->
-<!-- <h2 id="general">General Optimizer Improvements</h2> -->
-
+<h2 id="general">General Optimizer Improvements</h2>
+  <ul>
+    <li>UndefinedBehaviorSanitizer gained a new sanitization option,
+	<code>-fsanitize=bounds-strict</code>, which enables strict checking
+	of array bounds.  In particular, it enables
+	<code>-fsanitize=bounds</code> as well as instrumentation of
+	flexible array member-like arrays.
+  </ul>
 
 <!-- .................................................................. -->
 <h2 id="languages">New Languages and Language specific improvements</h2>
 
 <!-- <h3 id="ada">Ada</h3> -->
 
-<!-- <h3 id="c-family">C family</h3> -->
+<h3 id="c-family">C family</h3>
+  <ul>
+    <li>A new command-line option <code>-Wshift-negative-value</code> has been
+	added for the C and C++ compilers, which warns about left shifting
+	a negative value.</li>
+  </ul>
+
+<h3 id="c">C</h3>
+  <ul>
+    <li>It is possible to disable warnings when an initialized field of
+	a structure or a union with side effects is being overridden when
+	using designated initializers via a new warning option
+	<code>-Woverride-init-side-effects</code>.</li>
+  </ul>
 
 <h3 id="cxx">C++</h3>
 

	Marek

  reply	other threads:[~2015-05-11 16:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-11 14:48 Marek Polacek
2015-05-11 16:04 ` Gerald Pfeifer
2015-05-11 16:17   ` Marek Polacek [this message]
2015-05-11 16:40     ` Gerald Pfeifer
  -- strict thread matches above, loose matches on Subject: below --
2015-05-25 10:25 Marek Polacek
2014-10-15 10:30 Marek Polacek
2014-10-15 10:51 ` Richard Biener
2014-10-15 11:09   ` Jakub Jelinek
2014-10-15 11:25     ` Marek Polacek
2014-10-15 11:10   ` Marek Polacek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150511161653.GR3384@redhat.com \
    --to=polacek@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).