From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 53338 invoked by alias); 1 Mar 2015 05:54:59 -0000 Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org Received: (qmail 53315 invoked by uid 89); 1 Mar 2015 05:54:58 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=4.5 required=5.0 tests=BAYES_40,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,KAM_FROM_URIBL_PCCC,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=no version=3.3.2 X-HELO: mail-la0-f48.google.com Received: from mail-la0-f48.google.com (HELO mail-la0-f48.google.com) (209.85.215.48) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Sun, 01 Mar 2015 05:54:57 +0000 Received: by labhs14 with SMTP id hs14so24551609lab.1 for ; Sat, 28 Feb 2015 21:54:46 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.112.155.98 with SMTP id vv2mr19381929lbb.121.1425189286254; Sat, 28 Feb 2015 21:54:46 -0800 (PST) Received: by 10.152.166.198 with HTTP; Sat, 28 Feb 2015 21:54:46 -0800 (PST) Date: Sun, 01 Mar 2015 05:54:00 -0000 Message-ID: Subject: User account creation has been restricted From: Dustin Boyd To: overseers@gcc.gnu.org Content-Type: text/plain; charset=UTF-8 X-SW-Source: 2015-q1/txt/msg00089.txt.bz2 I was going to report a bug, or what seems to be a bug, but when I tried to create an account, I received the following error: ==== User account creation has been restricted. Contact your administrator or the maintainer (overseers@gcc.gnu.org) for information about creating an account. ==== It's a small bug with C99 VLAs I just encountered on mingw-w64 that only sometimes resulting in a warning diagnostic. If I could test other targets, I would. I just downloaded TDM-GCC 4.8.2, and it happens using that compiler as well as with my own GCC 4.9.1 compiler I built a few months ago, both of which target mingw-w64. I'd love to report it to someone who could put it into the issue tracker at the very least, so if that's an option, I'd be happy to do that as well.