From: Gonzalez Pedro <gonzalez.rulez@gmail.com>
To: overseers@gcc.gnu.org
Subject: User account creation has been restricted
Date: Fri, 31 Oct 2014 07:29:00 -0000 [thread overview]
Message-ID: <CACdjoLGET88+7mWzNFFYTdv0cmDYA26r=_Pm+ir4zAyxNFRk5Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]
hello,
I wanted to create account to submit bug, but got back this error message:
User account creation has been restricted.
Contact your administrator or the maintainer (overseers@gcc.gnu.org)
for information about creating an account.
Anyway, here are the bug details
Title:
Temporary object stack space is not re-used
Related to:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51060
Description:
The only difference between this issue and 51060 is that code is being
compiled without "Os".
$ g++ -c 51060.cpp -Wframe-larger-than=2048 -Werror
51060.cpp: In function ‘void Test()’:
51060.cpp:37:1: error: the frame size of 10240 bytes is larger than
2048 bytes [-Werror=frame-larger-than=]
}
^
cc1plus: all warnings being treated as errors
See attached code sample.
Environment:
$ g++ --version
g++ (GCC) 4.8.3 20140911 (Red Hat 4.8.3-7)
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$ uname -s -r -v -p -i -o
Linux 3.16.6-200.fc20.x86_64 #1 SMP Wed Oct 15 13:06:51 UTC 2014
x86_64 x86_64 GNU/Linux
[-- Attachment #2: 51060.cpp --]
[-- Type: text/x-c++src, Size: 662 bytes --]
//
// Shows a problem of not re-using stack space:
// Compile as: g++ -c 51060.cpp -Wframe-larger-than=2048 -Werror
// Result: warning: the frame size of 10240 bytes is larger than 2048 bytes [-Wframe-larger-than=]
//
#include <iostream>
struct StackObject
{
StackObject()
{
// prevent optimization
buffer[0] = 0;
std::cerr << buffer;
}
char buffer[1024];
};
void Test()
{
#define TEST_SUB() \
{ StackObject(); }
#define TEST() \
TEST_SUB() \
TEST_SUB() \
TEST_SUB() \
TEST_SUB() \
TEST_SUB() \
TEST_SUB() \
TEST_SUB() \
TEST_SUB() \
TEST_SUB() \
TEST_SUB()
TEST()
}
next reply other threads:[~2014-10-29 15:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 7:29 Gonzalez Pedro [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-21 18:37 Guy
2021-12-21 19:16 ` Frank Ch. Eigler
2021-12-21 19:19 ` Christopher Faylor
2017-03-05 8:52 Tino Calancha
2015-03-01 5:54 Dustin Boyd
2015-01-27 7:20 Vladimir Stackov
2014-10-29 15:16 Eric Shattow
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='CACdjoLGET88+7mWzNFFYTdv0cmDYA26r=_Pm+ir4zAyxNFRk5Q@mail.gmail.com' \
--to=gonzalez.rulez@gmail.com \
--cc=overseers@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).