public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: chrisb@funcom.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/6404: Internal compiler error when compiling with extended block profiling.
Date: Mon, 22 Apr 2002 05:46:00 -0000	[thread overview]
Message-ID: <20020422124108.12286.qmail@sources.redhat.com> (raw)


>Number:         6404
>Category:       c++
>Synopsis:       Internal compiler error when compiling with extended block profiling.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Apr 22 05:46:02 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     chrisb@funcom.com
>Release:        gcc 3.0.4
>Organization:
>Environment:
i386
>Description:
Compiling with extended block profiling causes internal compiler error.

[chrisb@test12 test]$ /home/chrisb/local/bin/gcc -c test.cpp
[chrisb@test12 test]$

[chrisb@test12 test]$ /home/chrisb/local/bin/gcc -c test.cpp -ax
test.cpp: In function `int Foo(float)':
test.cpp:6: Unrecognizable insn:
(call_insn 42 41 43 (call (mem:QI (symbol_ref ("__bb_trace_ret")) 0)
        (const_int 0 [0x0])) -1 (nil)
    (nil)
    (nil))
test.cpp:6: Internal compiler error in insn_default_length, at insn-attrtab.c:
   223
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
>How-To-Repeat:
gcc -c test.cpp -ax
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/plain; name="test.cpp"
Content-Disposition: inline; filename="test.cpp"

#include <stdio.h>

int Foo(float abra)
{
  return (int) abra;
}

int
main(int argc, char **argv)
{
  int n = Foo(1.5f);
  printf("%d\n", n);

  int *a = new int;

  printf("a=%d\n", a);
}


             reply	other threads:[~2002-04-22 12:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-22  5:46 chrisb [this message]
2002-04-24 19:55 rodrigc

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=20020422124108.12286.qmail@sources.redhat.com \
    --to=chrisb@funcom.com \
    --cc=gcc-gnats@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).