From: "Mike Frysinger" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage:master commit in: doc/
Date: Thu, 30 Jul 2015 08:10:50 +0000 (UTC) [thread overview]
Message-ID: <1438243796.0cd8097a6e28908f22d76c714f2baeb2da5139d9.vapier@gentoo> (raw)
commit: 0cd8097a6e28908f22d76c714f2baeb2da5139d9
Author: Mike Frysinger <vapier <AT> gentoo <DOT> org>
AuthorDate: Thu Jul 30 08:09:56 2015 +0000
Commit: Mike Frysinger <vapier <AT> gentoo <DOT> org>
CommitDate: Thu Jul 30 08:09:56 2015 +0000
URL: https://gitweb.gentoo.org/proj/portage.git/commit/?id=0cd8097a
doc: add another strict aliasing link
doc/qa.docbook | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/doc/qa.docbook b/doc/qa.docbook
index d0986e2..6e25714 100644
--- a/doc/qa.docbook
+++ b/doc/qa.docbook
@@ -224,7 +224,8 @@
For information, please review these links:
<ulink url="http://mail-index.netbsd.org/tech-kern/2003/08/11/0001.html">NetBSD Explanation</ulink>,
<ulink url="http://thread.gmane.org/gmane.linux.gentoo.devel/39495">Gentoo Dev Thread</ulink>,
- <ulink url="http://gcc.gnu.org/bugs.html#nonbugs_c">GCC Docs</ulink>
+ <ulink url="http://gcc.gnu.org/bugs.html#nonbugs_c">GCC Docs</ulink>,
+ <ulink url="http://cellperformance.beyond3d.com/articles/2006/06/understanding-strict-aliasing.html">Practical examples</ulink>.
</para>
<para>
To fix this issue, use the methods proposed in the links mentioned earlier.
next reply other threads:[~2015-07-30 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 8:10 Mike Frysinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-09-19 8:51 [gentoo-commits] proj/portage:master commit in: doc/ Zac Medico
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=1438243796.0cd8097a6e28908f22d76c714f2baeb2da5139d9.vapier@gentoo \
--to=vapier@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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