public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: hpc@prism.uvsq.fr
To: gcc-gnats@gcc.gnu.org
Cc: jalby.prism.uvsq.fr@sources.redhat.com, kbrifa@prism.uvsq.fr
Subject: target/7349: ia64 function pointer :
Date: Thu, 18 Jul 2002 06:26:00 -0000	[thread overview]
Message-ID: <20020718132302.842.qmail@sources.redhat.com> (raw)


>Number:         7349
>Category:       target
>Synopsis:       ia64 function pointer :
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          wrong-code
>Submitter-Id:   net
>Arrival-Date:   Thu Jul 18 06:26:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Henri-Pierre Charles
>Release:        gcc version 2.96
>Organization:
>Environment:
Linux malraux 2.4.18 #2 SMP Tue Jul 9 11:28:20 CEST 2002 ia64 unknown
>Description:
The generated code for the program is not correct.It seem that without -O the third call are not correct.

This code compiler correctly on Solaris/sparc, 
FreeBSD/i386, linux/i386.
>How-To-Repeat:
Compile & execute without -O on an ia64 platform
>Fix:
None actually
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="TestBug.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="TestBug.c"

I2luY2x1ZGUgPHN0cmluZy5oPgojaW5jbHVkZSA8c3RkaW8uaD4KCnR5cGVkZWYgIGludCAoKnBm
aWlpKShpbnQsIGludCk7CgppbnQgYWRkKGludCBhLCBpbnQgYikKewogIHJldHVybiBhK2I7Cn0g
LyogYWRkICovCgppbnQgYmlkb24oaW50IGEsIGludCBiKQp7Cn0gLyogYWRkICovCgppbnQgbWFp
bihpbnQgYXJnYywgY2hhciAqIGFyZ3ZbXSkKewogIGNoYXIgY29kZUJ1ZmZlcjFbMTAyNF07CiAg
Y2hhciAqY29kZUJ1ZmZlcjIgPSAoY2hhciAqKSBjYWxsb2MgKDEwMjQsIDEpOwogIHBmaWlpIG15
RnVuY3Rpb247CiAgKHZvaWQpIHByaW50ZigiJWQgJWRcbiIsIDYsIGFkZCAoNiwgMzYpKTsKICBi
Y29weSAoYWRkLCBjb2RlQnVmZmVyMSwgMTAyNCk7CiAgbXlGdW5jdGlvbiA9IChwZmlpaSkgY29k
ZUJ1ZmZlcjE7CiAgKHZvaWQpIHByaW50ZigiJWQgJWRcbiIsIDcsIG15RnVuY3Rpb24oNywgMzUp
KTsKICBiY29weSAoYWRkLCBjb2RlQnVmZmVyMiwgMTAyNCk7CiAgbXlGdW5jdGlvbiA9IChwZmlp
aSkgY29kZUJ1ZmZlcjI7CiAgKHZvaWQpIHByaW50ZigiJWQgJWRcbiIsIDgsIG15RnVuY3Rpb24o
OCwgMzQpKTsKICBmcmVlIChjb2RlQnVmZmVyMik7CiAgcmV0dXJuIDA7Cn0K


             reply	other threads:[~2002-07-18 13:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-18  6:26 hpc [this message]
2002-10-10 17:15 janis

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=20020718132302.842.qmail@sources.redhat.com \
    --to=hpc@prism.uvsq.fr \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=jalby.prism.uvsq.fr@sources.redhat.com \
    --cc=kbrifa@prism.uvsq.fr \
    /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).