Re: Version specific onlinedocs page
Gerald Pfeifer wrote: On Sun, 17 Feb 2013, Tobias Burnus wrote: I wonder if we could generate a version-specific page for the online documentation. I think that should be trivial to maintain and I know at least one vendor who would use it. If "we" means that you are volunteering ;-), absolutely, go for it! ;-) How about the following patch? If it is okay, I will add the remaining index.html for 4.6 and 4.7 and update gcc-4.6/index.html – and then commit it. (I don't see a need to update versions before 4.6.) Tobias Index: htdocs/gcc-4.7/index.html === RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.7/index.html,v retrieving revision 1.4 diff -u -p -r1.4 index.html --- htdocs/gcc-4.7/index.html 20 Sep 2012 06:31:19 - 1.4 +++ htdocs/gcc-4.7/index.html 18 Feb 2013 07:49:34 - @@ -22,17 +22,20 @@ in GCC 4.7.1 relative to previous releas GCC 4.7.2 September 20, 2012 -(changes) +(changes, + http://www.gnu.org/onlinedocs/4.7.2/";>documentation) GCC 4.7.1 June 14, 2012 -(changes) +(changes, + http://www.gnu.org/onlinedocs/4.7.1/";>documentation) GCC 4.7.0 March 22, 2012 -(changes) +(changes, + http://www.gnu.org/onlinedocs/4.7.0/";>documentation) Index: htdocs/releasing.html === RCS file: /cvs/gcc/wwwdocs/htdocs/releasing.html,v retrieving revision 1.39 diff -u -p -r1.39 releasing.html --- htdocs/releasing.html 23 Mar 2012 08:44:11 - 1.39 +++ htdocs/releasing.html 18 Feb 2013 07:49:34 - @@ -75,7 +75,9 @@ to generate the documentation would be < -rgcc_3_0_2_release -dgcc-3.0.2 (with the current version number inserted). Link to it from onlinedocs/index.html (but don't break URLs to documentation for previous releases even if -you remove the links to it). +you remove the links to it). Create additionally +onlinedocs/version-number/index.html to link +to the documentation. Update the online-documentation links in changes.html to point to the online-documentation for the branch. --- /dev/null 2013-02-18 07:34:01.727808559 +0100 +++ htdocs/onlinedocs/4.7.2/index.html 2013-02-18 08:47:51.0 +0100 @@ -0,0 +1,90 @@ + + + +GCC 4.7.2 manuals + + + + +4.7.2 manuals + +http://gcc.gnu.org/onlinedocs/gcc-4.7.2/gcc/";>GCC + 4.7.2 Manual (http://gcc.gnu.org/onlinedocs/gcc-4.7.2/gcc.pdf";>also + in PDF or http://gcc.gnu.org/onlinedocs/gcc-4.7.2/gcc.ps.gz";>PostScript or http://gcc.gnu.org/onlinedocs/gcc-4.7.2/gcc-html.tar.gz";>an + HTML tarball) +http://gcc.gnu.org/onlinedocs/gcc-4.7.2/gfortran/";>GCC + 4.7.2 GNU Fortran Manual (http://gcc.gnu.org/onlinedocs/gcc-4.7.2/gfortran.pdf";>also + in PDF or http://gcc.gnu.org/onlinedocs/gcc-4.7.2/gfortran.ps.gz";>PostScript or http://gcc.gnu.org/onlinedocs/gcc-4.7.2/gfortran-html.tar.gz";>an + HTML tarball) +http://gcc.gnu.org/onlinedocs/gcc-4.7.2/gcj/";>GCC + 4.7.2 GCJ Manual (http://gcc.gnu.org/onlinedocs/gcc-4.7.2/gcj.pdf";>also + in PDF or http://gcc.gnu.org/onlinedocs/gcc-4.7.2/gcj.ps.gz";>PostScript or http://gcc.gnu.org/onlinedocs/gcc-4.7.2/gcj-html.tar.gz";>an + HTML tarball) +http://gcc.gnu.org/onlinedocs/gcc-4.7.2/cpp/";>GCC + 4.7.2 CPP Manual (http://gcc.gnu.org/onlinedocs/gcc-4.7.2/cpp.pdf";>also + in PDF or http://gcc.gnu.org/onlinedocs/gcc-4.7.2/cpp.ps.gz";>PostScript or http://gcc.gnu.org/onlinedocs/gcc-4.7.2/cpp-html.tar.gz";>an + HTML tarball) +http://gcc.gnu.org/onlinedocs/gcc-4.7.2/gnat_rm/";>GCC + 4.7.2 GNAT Reference Manual (http://gcc.gnu.org/onlinedocs/gcc-4.7.2/gnat_rm.pdf";>also + in PDF or http://gcc.gnu.org/onlinedocs/gcc-4.7.2/gnat_rm.ps.gz";>PostScript or http://gcc.gnu.org/onlinedocs/gcc-4.7.2/gnat_rm-html.tar.gz";>an + HTML tarball) +http://gcc.gnu.org/onlinedocs/gcc-4.7.2/gnat_ugn_unw/";>GCC + 4.7.2 GNAT User's Guide (http://gcc.gnu.org/onlinedocs/gcc-4.7.2/gnat_ugn_unw.pdf";>also + in PDF or http://gcc.gnu.org/onlinedocs/gcc-4.7.2/gnat_ugn_unw.ps.gz";>PostScript or http://gcc.gnu.org/onlinedocs/gcc-4.7.2/gnat_ugn_unw-html.tar.gz";>an + HTML tarball) +http://gcc.gnu.org/onlinedocs/gcc-4.7.2/libstdc++/manual/";>GCC + 4.7.2 Standard C++ Library Manual (http://gcc.gnu.org/onlinedocs/gcc-4.7.2/libstdc++/libstdc++-manual.pdf.bz2";>also + in PDF or http://gcc.gnu.org/onlinedocs/gcc-4.7.2/libstdc++/libstdc++-manual.xml.bz2";>XML or http://gcc.gnu.org/onlinedocs/gcc-4.7.2/libstdc++/libstdc++-manual-html.tar.bz2";>an + HTML tarball) +http://gcc.gnu.org/onlinedocs/gcc-4.7.2/libstdc++/api/";>GCC + 4.7.2 Standard C++ Library Reference Manual (http://gcc.gnu.org/onlinedocs/gcc-4.7.2/libstdc++/libstdc++-api.pdf.bz2";>also + in PDF or http://gcc.gnu.org/onlinedocs/gcc-4.7.2/libstdc++/libstdc++-api.xml.bz2";>XML or http://gcc.gnu.org/onli
Re: [GCC 4.8 wwwdocs] PATCH: Mention several user-visible changes for x86
On 18 February 2013 00:07:33 Gerald Pfeifer wrote: On Fri, 15 Feb 2013, Igor Zamyatin wrote: > Is it ok for wwwdocs? Index: htdocs/gcc-4.8/changes.html === + x86 backend was improved to allow option -fscedule-insns to work reliably. "The x86 backend has been improved..." I really hope that there is no such option. Sent with AquaMail for Android http://www.aqua-mail.com
Re: [GCC 4.8 wwwdocs] PATCH: Mention several user-visible changes for x86
Gerald, Thanks a lot for your remarks! Below is updated patch which will be checked in. Thanks, Igor On Mon, Feb 18, 2013 at 3:07 AM, Gerald Pfeifer wrote: > On Fri, 15 Feb 2013, Igor Zamyatin wrote: >> Is it ok for wwwdocs? > > Index: htdocs/gcc-4.8/changes.html > === > + Support for the new Intel processor codename Broadwell with RDSEED, > + ADCX, ADOX, PREFETCHW is available through -madx, > + -mprfchw, -mrdseed. > > Can you make this RDSEED, ... and so forth? > (This is a bit borderline, in that one could also see this as > more general references, but usually we mark those up.) > > And "...through the ... command-line options."? > > + Support for Intel RTM and HLE intrinsics, built-in > > "the ... intrinsics" (and same below for "instruction sets") > > + x86 backend was improved to allow option > -fscedule-insns to work reliably. > > "The x86 backend has been improved..." > > + This option can be used to schedule instructions better and can > lead to improved performace in certain cases. > > This line is quite long, can you break lines around 76 columns? > > And, let's be a bit more brave and omit either "can" or "in certain > cases". Otherwise this may sounds too unlikely. :-) > > The patch is fine with changes along the lines described above. > > Thanks, > Gerald Index: htdocs/gcc-4.8/changes.html === RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.8/changes.html,v retrieving revision 1.95 diff -c -r1.95 changes.html *** htdocs/gcc-4.8/changes.html 11 Feb 2013 15:12:58 - 1.95 --- htdocs/gcc-4.8/changes.html 12 Feb 2013 15:10:41 - *** *** 460,465 --- 460,471 wrong results. You must build all modules with -mpreferred-stack-boundary=3, including any libraries. This includes the system libraries and startup modules. + Support for the new Intel processor codename Broadwell with + RDSEED, ADCX, ADOX, + PREFETCHW is available through -madx, + -mprfchw, -mrdseed command-line options. + + Support for the Intel RTM and HLE intrinsics, built-in functions and code generation is available via -mrtm and -mhle. + + Support for the Intel FXSR, XSAVE and XSAVEOPT instruction sets. Intrinsics and built-in functions are available + via -mfxsr, -mxsave and -mxsaveopt respectively. + New built-in functions to detect run-time CPU type and ISA: A built-in function __builtin_cpu_is has been added to *** *** 524,529 --- 530,538 http://gcc.gnu.org/wiki/FunctionMultiVersioning";>wiki for more information. + The x86 backend has been improved to allow option -fscedule-insns to work reliably. + This option can be used to schedule instructions better and leads to + improved performace in certain cases. + Windows MinGW-w64 targets (*-w64-mingw*) require at least r5437 from the Mingw-w64 trunk.
RE: [PATCH] Fix PR50293 - LTO plugin with space in path
Joseph, Thanks for your valuable comments. See my reply and new patch below.
> -Original Message-
> From: Joseph Myers [mailto:jos...@codesourcery.com]
> Sent: Monday, February 18, 2013 06:16
> To: Joey Ye
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] Fix PR50293 - LTO plugin with space in path
>
> On Sun, 17 Feb 2013, Joey Ye wrote:
>
> > +static char * convert_white_space(char * orig);
>
> Please fix formatting in many places in this patch to follow the GNU
> Coding Standards. No space after '*', but space before '('; there seem
> to
> be various other formatting problems as well.
My bad. All fixed.
>
> > +/* Insert back slash before spaces in a string, to avoid path
> > + that has space in it broken into multiple arguments. */
>
> That doesn't seem to be a proper specification of the interface to this
> function. What are the semantics of ORIG? A string that is a filename,
> or something else? What are the exact semantics of the return value for
> quoting - is it correct for the function to convert a (backslash, space)
> pair to (backslash, backslash, space) or not? Is anything special in
> the
> return value other than backslash and space, and how are any special
> characters in the return value to be interpreted?
>
> As it seems like this function frees the argument (why?) this also needs
> to be specified in the comment as part of the semantics of the function.
This function might need a string longer than original one to accommodate
additional back slashes. So it has to xmalloc a new string. The original
string should be freed in such a case. However, it is tedious to caller
to figure out that conversion does happens and free the orig. The solution
is for this function to free it when conversion happens.
By doing so it is required that orig must be allocated and can be freed,
as the newly added comments described explicitly.
>
> It would be a good idea for you to give a more detailed explanation in
> the
> next version of the patch submission of how the path, before the patch,
> got processed so that the spaces were wrongly interpreted. That might
> help make clearer whether the interface to this new function is actually
> correct, since the subsequent operations on the return value should act
> as
> an inverse to the operation carried out by this function.
>
> --
> Joseph S. Myers
> jos...@codesourcery.com
Index: gcc/gcc.c
===
--- gcc/gcc.c (revision 195189)
+++ gcc/gcc.c (working copy)
@@ -265,6 +265,7 @@
static const char *compare_debug_auxbase_opt_spec_function (int, const char
**);
static const char *pass_through_libs_spec_func (int, const char **);
static const char *replace_extension_spec_func (int, const char **);
+static char * convert_white_space (char *);
/* The Specs Language
@@ -6595,6 +6596,7 @@
X_OK, false);
if (lto_wrapper_file)
{
+ lto_wrapper_file = convert_white_space (lto_wrapper_file);
lto_wrapper_spec = lto_wrapper_file;
obstack_init (&collect_obstack);
obstack_grow (&collect_obstack, "COLLECT_LTO_WRAPPER=",
@@ -7005,12 +7007,13 @@
+ strlen (fuse_linker_plugin), 0))
#endif
{
- linker_plugin_file_spec = find_a_file (&exec_prefixes,
+ char * temp_spec = find_a_file (&exec_prefixes,
LTOPLUGINSONAME, R_OK,
false);
- if (!linker_plugin_file_spec)
+ if (!temp_spec)
fatal_error ("-fuse-linker-plugin, but %s not found",
LTOPLUGINSONAME);
+ linker_plugin_file_spec = convert_white_space (temp_spec);
}
#endif
lto_gcc_spec = argv[0];
@@ -8506,3 +8509,52 @@
free (name);
return result;
}
+
+/* Insert back slash before spaces in orig (usually a file path), to
+ avoid being broken by spec parser.
+
+ This function is needed as do_spec_1 treats white space (' ' and '\t')
+ as the end of an argument. But in case of -plugin /usr/gcc
install/xxx.so,
+ the filename should be treated as a single argument rather than being
+ broken into multiple. Solution is to insert '\\' before the space in a
+ filename.
+
+ This function converts and only converts all occurrance of ' '
+ to '\\' + ' ' and '\t' to '\\' + '\t'. For example:
+ "a b" -> "a\\ b"
+ "a b" -> "a\\ \\ b"
+ "a\tb" -> "a\\\tb"
+ "a\\ b" -> "a b"
+
+ orig: input null-terminating string that was allocated by xalloc. The
+ memory it points to might be freed in this function. Behavior undefined
+ if orig isn't xalloced or is freed already at entry.
+
+ Return: orig if no conversion needed. orig if conversion needed but no
+ sufficient memory for a new string. Otherwise a newly allocated string
+ that was converted from orig. */
+
+static
Re: [GCC 4.8 wwwdocs] PATCH: Mention several user-visible changes for x86
On Fri, 15 Feb 2013, Igor Zamyatin wrote: > Is it ok for wwwdocs? Index: htdocs/gcc-4.8/changes.html === + Support for the new Intel processor codename Broadwell with RDSEED, + ADCX, ADOX, PREFETCHW is available through -madx, + -mprfchw, -mrdseed. Can you make this RDSEED, ... and so forth? (This is a bit borderline, in that one could also see this as more general references, but usually we mark those up.) And "...through the ... command-line options."? + Support for Intel RTM and HLE intrinsics, built-in "the ... intrinsics" (and same below for "instruction sets") + x86 backend was improved to allow option -fscedule-insns to work reliably. "The x86 backend has been improved..." + This option can be used to schedule instructions better and can lead to improved performace in certain cases. This line is quite long, can you break lines around 76 columns? And, let's be a bit more brave and omit either "can" or "in certain cases". Otherwise this may sounds too unlikely. :-) The patch is fine with changes along the lines described above. Thanks, Gerald
Re: [PATCH] Fix PR50293 - LTO plugin with space in path
On Sun, 17 Feb 2013, Joey Ye wrote:
> +static char * convert_white_space(char * orig);
Please fix formatting in many places in this patch to follow the GNU
Coding Standards. No space after '*', but space before '('; there seem to
be various other formatting problems as well.
> +/* Insert back slash before spaces in a string, to avoid path
> + that has space in it broken into multiple arguments. */
That doesn't seem to be a proper specification of the interface to this
function. What are the semantics of ORIG? A string that is a filename,
or something else? What are the exact semantics of the return value for
quoting - is it correct for the function to convert a (backslash, space)
pair to (backslash, backslash, space) or not? Is anything special in the
return value other than backslash and space, and how are any special
characters in the return value to be interpreted?
As it seems like this function frees the argument (why?) this also needs
to be specified in the comment as part of the semantics of the function.
It would be a good idea for you to give a more detailed explanation in the
next version of the patch submission of how the path, before the patch,
got processed so that the spaces were wrongly interpreted. That might
help make clearer whether the interface to this new function is actually
correct, since the subsequent operations on the return value should act as
an inverse to the operation carried out by this function.
--
Joseph S. Myers
jos...@codesourcery.com
Re: [wwwdocs] Buildstat update for 4.7
On Mon, 4 Feb 2013, Tom G. Christensen wrote: > Latest results for 4.7.x Thanks Tom, applied. Gerald
Re: [GCC 4.8 changes] PATCH: Mention -maddress-mode=[short|long]
On Mon, 11 Feb 2013, H.J. Lu wrote: > This patch updates GCC 4.8 changes.html to mention > -maddress-mode=[short|long] for x32. OK to install? I made two tweaks on top. If you can get a colleague who is a native speaker to have a look, there may be more clarifications/ improvements to make. Gerald Index: changes.html === RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.8/changes.html,v retrieving revision 1.101 diff -u -3 -p -r1.101 changes.html --- changes.html17 Feb 2013 12:40:57 - 1.101 +++ changes.html17 Feb 2013 19:05:55 - @@ -465,10 +465,10 @@ B b(42); // OK wrong results. You must build all modules with -mpreferred-stack-boundary=3, including any libraries. This includes the system libraries and startup modules. -New -maddress-mode=[short|long] option for x32. +New -maddress-mode=[short|long] options for x32. -maddress-mode=short overrides default 64-bit addresses to -32-bit by emitting 0x67 address-size override prefix. This -is the default address mode for x32. +32-bit by emitting the 0x67 address-size override prefix. +This is the default address mode for x32. New built-in functions to detect run-time CPU type and ISA: A built-in function __builtin_cpu_is has been added to
Re: [Patch, microblaze]: Handle 0x80000000 as 32bit signed dividend
On 02/10/2013 10:38 PM, David Holsgrove wrote: Handle 0x8000 as 32bit signed dividend Changelog 2013-02-11 Edgar E. Iglesias * config/microblaze/modsi3.S (modsi3): Fix case with 0x8000 as dividend. Is there a test case? -- Michael Eagerea...@eagercon.com 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
Re: [Patch, microblaze]: Free variable local allocs at block ends
On 02/10/2013 10:38 PM, David Holsgrove wrote: Free variable local allocs at block ends. Changelog 2013-02-11 Edgar E. Iglesias * config/microblaze/microblaze.md (save_stack_block): Define. (restore_stack_block): Likewise. Committed revision 196110. -- Michael Eagerea...@eagercon.com 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
[Patch, libquadmath, committed] fix signbit call (was: Re: Test failures when compiling gfortran/libquadmath with -O0)
Tilo Schwarz wrote: I built gfortran with -O0 in order to follow some gfortran code paths in gdb. Now I noticed, that many of the tests in the fortran testsuite fail, because of .../gcc/build/i686-pc-linux-gnu/./libquadmath/.libs/libquadmath.so: undefined reference to `signbit' I was wondering - if that is on purpose - if I am doing something wrong - if there is an easy workaround (trying to link with -lm did not help). I think it is a bug of mine (from 2012-11-01) when converting from GLIBC. signbit is a macro which gets translated into __signbitf/__signbit/__signbitl; thus, "signbit" is not in any library. Still, I don't understand why it only fails without optimization – I had expected that it either gets translated into __signbitl – thus, "signbit" shouldn't appear in the error message. Or that is remains as is – but that should fail also with optimization. I have now committed the attached patch (as Rev. 196109). Tobias PS: At some point (in 4.9), the following commits should be ported from GLIBC to libquadmath: Fix casinh spurious underflows away from [-i,i] (bug 15062). Fix cacos real-part inaccuracy for result real part near 0 (bug 15023). Fix casinh, casin overflow (bug 14996). Fix casinh, casin inaccuracy from cancellation (bug 14994). Fix powl inaccuracy for x86_64 and x86 (bug 13881). and finally get some test-suite running, based on the GLIBC version. Index: libquadmath/ChangeLog === --- libquadmath/ChangeLog (Revision 196108) +++ libquadmath/ChangeLog (Arbeitskopie) @@ -1,3 +1,7 @@ +2013-02-17 Tobias Burnus + + * math/cacoshq.c (cacoshq): Call signbitq instead of signbit. + 2013-02-06 Richard Sandiford Revert previous patch. Index: libquadmath/math/cacoshq.c === --- libquadmath/math/cacoshq.c (Revision 196108) +++ libquadmath/math/cacoshq.c (Arbeitskopie) @@ -70,7 +70,7 @@ some cases. */ res = 2.0Q * clogq (csqrtq ((x + 1.0Q) / 2.0Q) + csqrtq ((x - 1.0Q) / 2.0Q)); - if (signbit (__real__ res)) + if (signbitq (__real__ res)) __real__ res = 0.0Q; } else
[wwwdocs] gcc-4.8/changes.html, C++ section
I noticed there were three "paragraphs" where HTML would pull them together into just one since it simply ignores blank lines. I marked them up with ... and used id= instead of . Applied Gerald Index: changes.html === RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.8/changes.html,v retrieving revision 1.100 diff -u -3 -p -r1.100 changes.html --- changes.html16 Feb 2013 14:48:25 - 1.100 +++ changes.html17 Feb 2013 12:37:13 - @@ -196,10 +196,9 @@ t.c:7:7: note: in expansion of macro 'MY --> - -C++ +C++ - G++ now implements the C++11 + G++ now implements the C++11 thread_local keyword; this differs from the GNU __thread keyword primarily in that it allows dynamic initialization and destruction semantics. Unfortunately, this support @@ -209,16 +208,16 @@ t.c:7:7: note: in expansion of macro 'MY initialization, so users may want to continue to use __thread for TLS variables with static initialization semantics. - + If the programmer can be sure that no use of the variable in a non-defining TU needs to trigger dynamic initialization (either because the variable is statically initialized, or a use of the variable in the defining TU will be executed before any uses in another TU), they can avoid this overhead with the -fno-extern-tls-init option. - + OpenMP threadprivate variables now also support dynamic -initialization and destruction by the same mechanism. - +initialization and destruction by the same mechanism. + G++ now implements the C++11 attribute syntax, e.g.
[wwwdocs] Rotate news
Applied. Gerald Index: index.html === RCS file: /cvs/gcc/wwwdocs/htdocs/index.html,v retrieving revision 1.870 diff -u -3 -p -r1.870 index.html --- index.html 16 Feb 2013 15:43:02 - 1.870 +++ index.html 17 Feb 2013 12:46:46 - @@ -90,48 +90,6 @@ Diego Novillo of Google. [2012-07-02] -GCC 4.7.1 released -[2012-06-14] - - -GCC 4.7.0 released -[2012-03-22] - - -GCC 4.4.7 released -[2012-03-13] - - -GCC 4.6.3 released -[2012-03-01] - - -CR16 processor support -[2012-02-02] -A port for National Semiconductor's CR16 processor has been contributed by -Sumanth Gundapaneni and Jayant Sonar of KPIT Cummins. - -TILE-Gx and TILEPro processor support -[2012-02-14] -Ports for the TILE-Gx and TILEPro families of processors have been -contributed by Walter Lee from Tilera. - -Atomic memory model support -[2011-11-06] -C++11/C11 http://gcc.gnu.org/wiki/Atomic/GCCMM";>memory model -support has been added through a new set of built-in __atomic -functions. Code was contributed by Andrew MacLeod, Richard Henderson, and -Aldy Hernandez, all of Red Hat, Inc. - - -GNU Tools Cauldron 2012 -[2011-11-18] -IUUK (Computer Science Institute, Charles University), CE-ITI -(Institute for Theoretical Computer Science) and Google are organizing -a http://gcc.gnu.org/wiki/cauldron2012";>workshop for GNU -Tools developers. The workshop will be held in July 2012 at -Charles University, Prague. - Index: news.html === RCS file: /cvs/gcc/wwwdocs/htdocs/news.html,v retrieving revision 1.134 diff -u -3 -p -r1.134 news.html --- news.html 1 Nov 2012 21:49:41 - 1.134 +++ news.html 17 Feb 2013 12:46:46 - @@ -14,6 +14,48 @@ +GCC 4.7.1 released +[2012-06-14] + + +GCC 4.7.0 released +[2012-03-22] + + +GCC 4.4.7 released +[2012-03-13] + + +GCC 4.6.3 released +[2012-03-01] + + +CR16 processor support +[2012-02-02] +A port for National Semiconductor's CR16 processor has been contributed by +Sumanth Gundapaneni and Jayant Sonar of KPIT Cummins. + +TILE-Gx and TILEPro processor support +[2012-02-14] +Ports for the TILE-Gx and TILEPro families of processors have been +contributed by Walter Lee from Tilera. + +Atomic memory model support +[2011-11-06] +C++11/C11 http://gcc.gnu.org/wiki/Atomic/GCCMM";>memory model +support has been added through a new set of built-in __atomic +functions. Code was contributed by Andrew MacLeod, Richard Henderson, and +Aldy Hernandez, all of Red Hat, Inc. + + +GNU Tools Cauldron 2012 +[2011-11-18] +IUUK (Computer Science Institute, Charles University), CE-ITI +(Institute for Theoretical Computer Science) and Google are organizing +a http://gcc.gnu.org/wiki/cauldron2012";>workshop for GNU +Tools developers. The workshop will be held in July 2012 at +Charles University, Prague. + Transactional memory support [2011-11-15] An implementation of the
