public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: Erwin.Unruh@fujitsu-siemens.com,
	Heinrich.Brand@fujitsu-siemens.com,
	Joachim.Canisius@fujitsu-siemens.com,
	Servatius.Brandt@fujitsu-siemens.com, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, rth@gcc.gnu.org
Subject: Re: middle-end/6348: internal error in allocate_dynamic_stack_space with STACK_SIZE_MODE non-default
Date: Sat, 15 Mar 2003 03:14:00 -0000	[thread overview]
Message-ID: <20030315031401.13753.qmail@sources.redhat.com> (raw)

Synopsis: internal error in allocate_dynamic_stack_space with STACK_SIZE_MODE non-default

Responsible-Changed-From-To: unassigned->rth
Responsible-Changed-By: bangerth
Responsible-Changed-When: Sat Mar 15 03:14:01 2003
Responsible-Changed-Why:
    Richard, you changed the lines around those in the patch 
    last, would you mind to take a look at this one and the 
    patch in the PR?
State-Changed-From-To: open->feedback
State-Changed-By: bangerth
State-Changed-When: Sat Mar 15 03:14:01 2003
State-Changed-Why:
    Seems like nobody has ever looked at this patch by now... :-(
    
    In any case, thank you for the patch. The code around this
    is still unchanged in present mainline. However, in order
    to check whether the patch is really necessary, it would
    be nice to have a testcase that actually triggers the
    compiler error you describe. This would also allow us to
    put something into the gcc testsuite so that this will
    not be broken again.
    
    Thanks
      Wolfgang

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6348


             reply	other threads:[~2003-03-15  3:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-15  3:14 bangerth [this message]
2003-03-20 22:52 rth

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=20030315031401.13753.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=Erwin.Unruh@fujitsu-siemens.com \
    --cc=Heinrich.Brand@fujitsu-siemens.com \
    --cc=Joachim.Canisius@fujitsu-siemens.com \
    --cc=Servatius.Brandt@fujitsu-siemens.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=rth@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).