From: Richard Sandiford <rdsandiford@googlemail.com>
To: gcc-patches@gcc.gnu.org
Subject: [wwwdocs] Mention MIPS changes for 4.8.
Date: Mon, 14 Jan 2013 19:04:00 -0000 [thread overview]
Message-ID: <87r4lny4bh.fsf@talisman.default> (raw)
Update the MIPS section of the 4.8 release notes. Please let me know
if I missed anything, or if you think the entries should be changed.
Committed.
Richard
Index: htdocs/gcc-4.8/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.8/changes.html,v
retrieving revision 1.82
retrieving revision 1.84
diff -u -r1.82 -r1.84
--- htdocs/gcc-4.8/changes.html 13 Jan 2013 11:29:33 -0000 1.82
+++ htdocs/gcc-4.8/changes.html 14 Jan 2013 19:01:03 -0000 1.84
@@ -481,11 +481,21 @@
<h3 id="mips">MIPS</h3>
<ul>
+ <li>GCC can now generate code specifically for the R4700, Broadcom XLP
+ and MIPS 34kn processors. The associated <code>-march</code> options
+ are <code>-march=r4700</code>, <code>-march=xlp</code>
+ and <code>-march=34kn</code> respectively.</li>
+ <li>GCC now generates better DSP code for MIPS 74k cores thanks
+ to further scheduling optimizations.</li>
+ <li>The MIPS port now supports the <code>-fstack-check</code>
+ option.</li>
<li>GCC now passes the <code>-mmcu</code> and <code>-mno-mcu</code>
- options to the assembler.</li>
- <li>Support for the R4700 has been added.</li>
- <li>GCC now generates better code for Broadcom XLP processors thanks
- to improvements in scheduling and atomic built-ins support.</li>
+ options to the assembler.</li>
+ <li>Previous versions of GCC would silently accept <code>-fpic</code>
+ and <code>-fPIC</code> for <code>-mno-abicalls</code> targets
+ like <code>mips*-elf</code>. This combination was not intended
+ or supported, and did not generate position-independent code.
+ GCC 4.8 now reports an error when this combination is used.</li>
</ul>
<h3 id="powerpc">PowerPC / PowerPC64 / RS6000</h3>
reply other threads:[~2013-01-14 19:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87r4lny4bh.fsf@talisman.default \
--to=rdsandiford@googlemail.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).