From: Tobias Burnus <burnus@net-b.de>
To: Benjamin De Kosnik <bkoz@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [wwwdocs] gcc-4.8/porting_to.html
Date: Wed, 13 Mar 2013 10:01:00 -0000 [thread overview]
Message-ID: <51404E84.3070903@net-b.de> (raw)
In-Reply-To: <20130313022916.0728c82e@oakwood>
Benjamin De Kosnik wrote:
> Hey! Here is the first pass at the 4.8 porting documentation.
>
> This seems to reflect the current trunk reality. I'm not quite sure to
> about the best way to talk about the more aggressive loop
> optimizations WRT undefined sematincs, but this seems reasonable. Of
> course, if anybody has better ideas, I'm all ears.
Could you then add a link to the porting guide from changes.html,
similar to last year's version? See
http://gcc.gnu.org/gcc-4.7/changes.html and search for "porting guide".
Tobias
next prev parent reply other threads:[~2013-03-13 10:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 9:29 Benjamin De Kosnik
2013-03-13 10:01 ` Tobias Burnus [this message]
2013-03-14 0:28 ` Benjamin De Kosnik
2013-03-14 1:23 ` Benjamin De Kosnik
2013-03-14 11:10 ` Alexander Monakov
2013-03-14 11:21 ` Jakub Jelinek
2013-03-13 10:27 ` Mikael Pettersson
2013-03-13 10:37 ` Alexander Monakov
2013-03-13 10:51 ` Mikael Pettersson
2013-03-14 0:26 ` Benjamin De Kosnik
2015-04-12 11:02 ` Gerald Pfeifer
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=51404E84.3070903@net-b.de \
--to=burnus@net-b.de \
--cc=bkoz@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
/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).