Fwd: IMPORTANT: sourceware.org hardware migration, MARCH 18..22
I am forwarding it as I only saw it on the fortran@gcc but not on the gcc@ list. Original Message Subject:IMPORTANT: sourceware.org hardware migration, MARCH 18..22 Date: Tue, 12 Mar 2013 11:36:04 -0400 (EDT) From: Frank Ch. Eigler Hi - Please be aware that **next week**, we will attempt to switch over the hardware that serves sourceware.org and its aliases (gcc.gnu.org, ecos.sourceware.org, cygwin.com, etc.) to newer & faster hardware donated by Red Hat. The plan is to take down network services next Monday around 14:00Z, and gradually bring things back up on the new machine, one service at a time, as quickly as possible. Since this change involves switching to a much younger OS and is complicated by many sourceware-specific services, the overall outage may last up to several days. We will prioritize getting source code version control systems up first. This announcement is being sent to those main mailing lists that have been recently active; please feel free to share it. You are welcome to listen in on irc.freenode.net #overseers during the transition period. We appreciate your patience and hope that the new machines will serve us all well. - FChE
Seemingly bogus FAILs in g++ testsuite.
Hi list,
I'm in the middle of a testsuite run and just saw the following FAILs crop up:
> FAIL: g++.old-deja/g++.brendan/cvt1.C (test for excess errors)
> FAIL: g++.old-deja/g++.brendan/enum11.C (test for excess errors)
> FAIL: g++.old-deja/g++.brendan/enum8.C (test for excess errors)
> FAIL: g++.old-deja/g++.brendan/enum9.C (test for excess errors)
> FAIL: g++.old-deja/g++.brendan/friend3.C (test for excess errors)
They all result from the same kind of error message, e.g.:
> /gnu/gcc/gcc/gcc/testsuite/g++.old-deja/g++.brendan/cvt1.C
> /gnu/gcc/gcc/gcc/testsuite/g++.old-deja/g++.brendan/cvt1.C:8:43: error: comma
> at end of enumerator list [-Wpedantic]
> /gnu/gcc/gcc/gcc/testsuite/g++.old-deja/g++.brendan/cvt1.C:18:44: error:
> comma at end of enumerator list [-Wpedantic]
> compiler exited with status 1
> output is:
> /gnu/gcc/gcc/gcc/testsuite/g++.old-deja/g++.brendan/cvt1.C:8:43: error: comma
> at end of enumerator list [-Wpedantic]
> /gnu/gcc/gcc/gcc/testsuite/g++.old-deja/g++.brendan/cvt1.C:18:44: error:
> comma at end of enumerator list [-Wpedantic]
>
> FAIL: g++.old-deja/g++.brendan/cvt1.C (test for excess errors)
> Excess errors:
> /gnu/gcc/gcc/gcc/testsuite/g++.old-deja/g++.brendan/cvt1.C:8:43: error: comma
> at end of enumerator list [-Wpedantic]
> /gnu/gcc/gcc/gcc/testsuite/g++.old-deja/g++.brendan/cvt1.C:18:44: error:
> comma at end of enumerator list [-Wpedantic]
Which is strange in two regards, because:
> $ cat -n /gnu/gcc/gcc/gcc/testsuite/g++.old-deja/g++.brendan/enum11.C
> 1 // { dg-do assemble }
> 2 // GROUPS passed enums
> 3 class X
> 4 {
> 5 enum
> 6 {
> 7 oneMask = 0x,
> 8 twoMask = 0x000F,
> 9 thiMask = 0xFFF0, // { dg-error "comma at end" "" { target
> c++98 } }
> 10 };
> 11 unsigned int foo;
> 12
> 13 public:
> 14 X (int) : foo (oneMask | twoMask ) {} // No warning
> 15 X (): foo (oneMask | twoMask | thiMask) {} // Warning
> 16 };
#1: Line 8 isn't the end of the enum list; line #9 is and it's correctly
tagged with dg-error
#2: There aren't even 18 lines in the source.
This doesn't appear to be happening on Linux (I'm using i686-pc-cygwin), so
is there some target-dependent support for the new error carets that needs
adding? (I'd guess not, and anyway, how would that turn one error into two,
but asking nonetheless). Has anyone else seen anything like this or got some
idea what might be going wrong?
cheers,
DaveK
Announce: GNU MPFR 3.1.2 is released
GNU MPFR 3.1.2 ("canard à l'orange", patch level 2) is now available
for download from the MPFR web site:
http://www.mpfr.org/mpfr-3.1.2/
from INRIAGForge:
https://gforge.inria.fr/projects/mpfr/
and from the GNU FTP site:
http://ftp.gnu.org/gnu/mpfr/
Thanks very much to those who sent us bug reports and/or tested the
release candidate.
The MD5's:
ee2c3ac63bf0c2359bf08fc3ee094c19 mpfr-3.1.2.tar.bz2
181aa7bb0e452c409f2788a4a7f38476 mpfr-3.1.2.tar.gz
e3d203d188b8fe60bb6578dd3152e05c mpfr-3.1.2.tar.xz
a25a48ed1b776f0cdc480338f1034617 mpfr-3.1.2.zip
The SHA1's:
46d5a11a59a4e31f74f73dd70c5d57a59de2d0b4 mpfr-3.1.2.tar.bz2
5ef83b835fe0a8bf29b7929394633252673e0d67 mpfr-3.1.2.tar.gz
03e593cc6e26639ef5e60be1af8dc527209e5172 mpfr-3.1.2.tar.xz
ed99cfc74a1df58953f3c2543e235587231a88ed mpfr-3.1.2.zip
The signatures:
http://www.mpfr.org/mpfr-3.1.2/mpfr-3.1.2.tar.xz.asc
http://www.mpfr.org/mpfr-3.1.2/mpfr-3.1.2.tar.bz2.asc
http://www.mpfr.org/mpfr-3.1.2/mpfr-3.1.2.tar.gz.asc
http://www.mpfr.org/mpfr-3.1.2/mpfr-3.1.2.zip.asc
Each tarball is signed by Vincent Lefèvre. This can be verified
using the DSA key ID 98C3739D; this key can be retrieved with:
gpg --recv-keys 98C3739D
or by downloading it from .
The key fingerprint is:
07F3 DBBE CC1A 3960 5078 094D 980C 1976 98C3 739D
The signatures can be verified with: gpg --verify
You should check that the key fingerprint matches.
Changes from version 3.1.1 to version 3.1.2:
- Bug fixes (see or ChangeLog file).
- Updated examples to the MPFR 3.x API.
Note: The official tarballs for MPFR up to 3.1.1 were affected by a
vulnerability for "make distcheck" due to a bug in old GNU Automake
versions: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-3386
One of the purposes of this release is to provide tarballs without
this vulnerability.
You can send success and failure reports to , and give
us the canonical system name (by running the "./config.guess" script),
the processor and the compiler version, in order to complete the
"Platforms Known to Support MPFR" section of the MPFR 3.1.2 web page.
Regards,
--
Vincent Lefèvre - Web:
gcc-4.8, summary command line changes
Hey people. I'm going through the 4.8 release and making notes of changes. Here are all the command line changes, summarized. I'm pleased to see that almost all of the new flags also have documentation. I can't find documentation for two changes (see below), perhaps the listed people can help me out? New flags, documentation in invoke.texi unless marked. 1. added -faggressive-loop-optimizations -fsanitize=thread -fsanitize=address -static-libasan --print-multiarch -imultilib (n, bug Matthias Klose ) -gsplit-dwarf -fira-hoist-pressure -fprofile-report -fopt-info -Og -flto-partition=max -fmem-report-wpa --no-sysroot-suffix -ftree-slsr -fstack-reuse=[all|name_vars|none] -floop-nest-optimize -gpubnames -fdelete-dead-exceptions -ftree-coalesce-inlined-vars -ftree-coalesce-vars -fhoist-adjacent-loads -fsync-libcalls -ftree-partial-pre -fsched-pressure-algorithm= (n, bug Richard Sandiford) -Wpedantic -fdiagnostics-show-caret 2. removed -dv -fsched-pressure-algorithm= -floop-flatten 3. deprecated -ftree-vectorizer-verbose 4. disabled -fipa-matrix-reorg (for all intents and purposes)
more 4.7 backports?
Last month I sent a list of bugreports that were 4.7 regressions, but had patches which fixed them for 4.8. It looks like ~7 of these had been backported and 10 more bugreports now exist with potential for backporting as well. Here are my rough notes: backported: 44061 - diagnostic 54767 - wrong-code 55043 - rejects-valid 55107 - compile-time-hog 55660 - [lto] ice-on-invalid 55890 - ice-on-invalid 53844 - missed-optimization (fixed back in July and waiting to see if any fallout?) - looks like it was backported, but then reverted? some discussion on... 54073 - missed-optimization 'not planning to backport it right now.' update: "I have moved this discussion to PR56309. Let's keep this PR open for eventual backport of the patch in Comment #13 to 4.7 branch." Not much activity on the remaining: 35634 - bad-code, however 'Unlikely going to be backported.' 43961 - [arm] target 48189 - ice-on-valid 48766 - ice-on-valid 51447 - wrong-code, however 'Could be back-ported, but IMHO this issue is not important enough for that so I'm not going to work on back-ports.' 53636 - wrong-code 53676 - missed-optimization (discussion about 4.7 backport after some more 4.8 exposure since August) 54051 - [arm] wrong-code? 54295 - wrong-code 54563 - ice-on-valid - already backported? *** 54919 - wrong-code, however 'no plans to work on back-ports of my patch for the release branches' 54974 - [arm] wrong-code (last comment was asking about 4.7 backport) 55018 - wrong-code 55614 - alignment issue/tree-optimization 55964 - ice New bug reports with potential backports: 56077 - wrong-code "Fixed on trunk, needs to be ported to 4.6/4.7 mid-Match." 56403 - ice-on-valid "The fix seems extremely safe, so I think backporting to 4.6 and 4.7 makes sense." 56470 - ice-on-valid "Fixed on trunk. Testing back-port to 4.7." 56608 - wrong-code - fixed on trunk 2013-03-13 56539 - wrong-code/ice-on-valid - fixed on trunk 2013-03-06 "The patch fixes the problem for both 4.7 and 4.8" 56270 - ice-on-valid - fixed on trunk 2013-03-05 56175 - missed-optimization - fixed on trunk 2013-02-25 new potential backports: 52448 - wrong-code - fixed on trunk 2013-02-08 48133 - ice-on-valid - fixed on trunk, but not clear where 45472 - ice (on-valid?) - fixed on trunk 2013-02-27 Hope this is useful. thanks, -Kenny
