public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/45962] [4.6 Regression]: many c/c++ failures on cris-elf, in r165236:165242
Date: Tue, 12 Oct 2010 21:55:00 -0000	[thread overview]
Message-ID: <20101012215500.NwrrtNX75xQwJxIoeuNBcea--TJyQoyK9_fm7xfaw0o@z> (raw)
In-Reply-To: <bug-45962-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45962

--- Comment #11 from Hans-Peter Nilsson <hp at gcc dot gnu.org> 2010-10-12 21:55:26 UTC ---
(In reply to comment #10)
> (In reply to comment #8)
> > I have to reopen this: the SEGV ICE is gone, but no regressions were fixed...
> 
> These aren't technically regressions; these tests were never run previously.
> I'm certain you'll find that ...
> 
> (In reply to comment #9)
> > I think I'm going to use gcc.c-torture/execute/simd-5.c at -O0.
> > I'll compare r165239 to (r165240 plus your commit at r165382), ok?
> 
> ... these tests fail with r165239 too, if you run them by hand.  If you
> just compare gcc.sum files of course they'll appear as new failures.

Incorrect.  I don't see what makes you say that.

> > #define STACK_BOUNDARY \
> >  (TARGET_STACK_ALIGN ? (TARGET_ALIGN_BY_32 ? 32 : 16) : 8)
> > (i.e. 8 for cris-elf default.)
> 
> This is definitely wrong, according to the documentation in the opt file.

Uh... what?  Ok, it's been a while since I wrote that part (which you can see
by the comment at the top of that macro!) so I might have to revisit that but
any such observation is incidental, because...

> You'd either have to multilib on this option, or implement the full stack
> re-alignment scheme supported by i386.  Unless you multilib:
> 
> STACK_BOUNDARY should be BITS_PER_UNIT always.

...it is; constant 8, for the purpose of this PR, as none of the options are
active.

Let's see how we can best proceed here.


  parent reply	other threads:[~2010-10-12 21:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-11  3:26 [Bug rtl-optimization/45962] New: " hp at gcc dot gnu.org
2010-10-11 17:27 ` [Bug rtl-optimization/45962] " rth at gcc dot gnu.org
2010-10-11 17:38 ` hp at gcc dot gnu.org
2010-10-11 17:38 ` hp at gcc dot gnu.org
2010-10-11 18:12 ` rth at gcc dot gnu.org
2010-10-11 22:46 ` [Bug middle-end/45962] " rth at gcc dot gnu.org
2010-10-12  2:31 ` hp at gcc dot gnu.org
2010-10-12 15:53 ` rth at gcc dot gnu.org
2010-10-12 15:55 ` rth at gcc dot gnu.org
2010-10-12 19:30 ` hp at gcc dot gnu.org
2010-10-12 20:23 ` hp at gcc dot gnu.org
2010-10-12 21:31 ` rth at gcc dot gnu.org
2010-10-12 21:55 ` hp at gcc dot gnu.org [this message]
2010-10-12 22:06 ` rth at gcc dot gnu.org
2010-10-12 22:16 ` hp at gcc dot gnu.org
2010-10-12 22:49 ` hp at gcc dot gnu.org
2010-10-19  2:38 ` hp at gcc dot gnu.org
2010-10-19 15:49 ` rth at gcc dot gnu.org
2010-10-19 22:22 ` hp at gcc dot gnu.org
2010-10-19 23:21 ` rth at gcc dot gnu.org
2010-11-03 15:39 ` rguenth at gcc dot gnu.org
2010-11-15 11:34 ` rguenth at gcc dot gnu.org
2011-03-11  4:42 ` hp at gcc dot gnu.org

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=20101012215500.NwrrtNX75xQwJxIoeuNBcea--TJyQoyK9_fm7xfaw0o@z \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).