public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tbm at cyrius dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/32337]  New: [4.3 Regression] Error: Register number out of range 0..1
Date: Thu, 14 Jun 2007 10:39:00 -0000	[thread overview]
Message-ID: <bug-32337-12387@http.gcc.gnu.org/bugzilla/> (raw)

I'm getting the following assembler error with current gcc 4.3.  This
worked with 20070604 and is probably due to the dataflow merge.


tbm@coconut0:~$ /usr/lib/gcc-snapshot/bin/gcc -c -O1 ccmalloc-callchain.c
ccmalloc-callchain.c: In function 'backtrace':
ccmalloc-callchain.c:14: warning: unsupported argument to
'__builtin_return_address'
/tmp/ccMB3CzF.s: Assembler messages:
/tmp/ccMB3CzF.s:10: Warning: Second operand of .save contradicts .prologue
/tmp/ccMB3CzF.s:17: Error: Register number out of range 0..1
/tmp/ccMB3CzF.s:17: Warning: Use of 'mov' violates WAW dependency 'GR%, % in 1
- 127' (impliedf), specific resource number is 33
/tmp/ccMB3CzF.s:17: Warning: Only the first path encountering the conflict is
reported
/tmp/ccMB3CzF.s:14: Warning: This is the location of the conflicting usage
/tmp/ccMB3CzF.s:39: Error: Register number out of range 0..1
/tmp/ccMB3CzF.s:60: Error: Register number out of range 0..1


Testcase:


typedef struct __jmp_buf_tag
{
}
jmp_buf[1];
static jmp_buf backtrace_jump;
static char *
return_address (unsigned i)
{
  switch (i)
    {
    case 0:
      return (char *) __builtin_return_address (0);
    case 1:
      return (char *) __builtin_return_address (1);
    }
}
backtrace (int skip)
{
  if (_setjmp (backtrace_jump) == 0)
    {
      int i = ++skip;
      while (1)
        {
          char *pc = return_address (i++);
          if (!pc)
            break;
        }
    }
}


-- 
           Summary: [4.3 Regression] Error: Register number out of range
                    0..1
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: tbm at cyrius dot com
GCC target triplet: ia64-linux-gnu


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


             reply	other threads:[~2007-06-14 10:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-14 10:39 tbm at cyrius dot com [this message]
2007-06-21 22:44 ` [Bug target/32337] " pinskia at gcc dot gnu dot org
2007-06-29 18:45 ` mmitchel at gcc dot gnu dot org
2007-07-04 16:35 ` jakub at gcc dot gnu dot org
2007-07-07 12:45 ` jakub at gcc dot gnu dot org
2007-09-17 22:30 ` jakub at gcc dot gnu dot 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=bug-32337-12387@http.gcc.gnu.org/bugzilla/ \
    --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).