public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Konstantin Serebryany <konstantin.s.serebryany@gmail.com>
To: Tobias Burnus <burnus@net-b.de>
Cc: gcc patches <gcc-patches@gcc.gnu.org>,
	Dodji Seketeli <dodji@redhat.com>,
		Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: [wwwdocs] Mention -faddress-sanitizer in gcc-4.8/changes.html
Date: Fri, 23 Nov 2012 13:25:00 -0000	[thread overview]
Message-ID: <CAGQ9bdxCN7YML=P2YGMi_5wKsh54qzPe9SSQY+j1qU0jbV+trQ@mail.gmail.com> (raw)
In-Reply-To: <50AF7893.6050407@net-b.de>

On Fri, Nov 23, 2012 at 5:22 PM, Tobias Burnus <burnus@net-b.de> wrote:
> Konstantin Serebryany wrote:
>>
>> Looks good.
>
>
> And now available at http://gcc.gnu.org/gcc-4.8/changes.html

Cool!

>
>
>>> Notes: I didn't mention Sparc, PowerPC, and Darwin
>>
>> Darwin works fine with clang, but not yet in gcc.
>
>
> I know – and actually it is a bit unclear to me what's the review status of
> Jack Howarth's patch.

I think it needs the LICENSE file (mach_override has a separate license).

>
>
>> at least simple tests for stack- and global- buffer overflows seem to
>> work.
>
>
> I think the man page should be then updated.

man page?


> (I think it used to mention
> stack and global buffer overflow; in any case, the the current version
> doesn't.)
>
> Tobias

  reply	other threads:[~2012-11-23 13:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-19 18:45 Tobias Burnus
2012-11-20  5:06 ` Konstantin Serebryany
2012-11-23 11:28   ` Tobias Burnus
2012-11-23 12:21     ` Konstantin Serebryany
2012-11-23 13:22       ` Tobias Burnus
2012-11-23 13:25         ` Konstantin Serebryany [this message]
2012-11-23 13:30           ` Tobias Burnus
2012-11-23 13:34             ` Konstantin Serebryany

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='CAGQ9bdxCN7YML=P2YGMi_5wKsh54qzPe9SSQY+j1qU0jbV+trQ@mail.gmail.com' \
    --to=konstantin.s.serebryany@gmail.com \
    --cc=burnus@net-b.de \
    --cc=dodji@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).