public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Franz.Sirl-kernel@lauterbach.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/6747: PPC: C++ rejects inline assembly, C works
Date: Mon, 20 May 2002 11:16:00 -0000	[thread overview]
Message-ID: <20020520181157.12036.qmail@sources.redhat.com> (raw)


>Number:         6747
>Category:       c++
>Synopsis:       PPC: C++ rejects inline assembly, C works
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Mon May 20 11:16:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Franz.Sirl-kernel@lauterbach.com
>Release:        gcc-3.1.x
>Organization:
>Environment:
powerpc-linux-gnu

Reading specs from /usr/lib/gcc-lib/ppc-linux/3.1.1/specs
Configured with: /home/fsirl/TC/gcc/BUILD/gcc-3.1.1/configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads --enable-checking=gc,misc,tree --enable-languages=c,c++,f77,objc --with-system-zlib ppc-linux
Thread model: posix
gcc version 3.1.1 20020519 (prerelease)
>Description:
The attached testcase fails if compiled with C++, compiling with C works fine. This is a regression from at least gcc-2.95.x and breaks OpenOffice builds on PPC.
>How-To-Repeat:
g++ -c -O2 test.cc -save-temps
test.cc: In function `void glibc_setfpucw(unsigned int)':
test.cc:21: output number 0 not directly addressable
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/x-csrc; name="test.ii"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="test.ii"

IyAxICJ0ZXN0LmNjIgojIDEgIjxidWlsdC1pbj4iCiMgMSAiPGNvbW1hbmQgbGluZT4iCiMgMSAi
dGVzdC5jYyIKIyAxNCAidGVzdC5jYyIKIyAxICIvdXNyL2luY2x1ZGUvZnB1X2NvbnRyb2wuaCIg
MSAzCiMgNDkgIi91c3IvaW5jbHVkZS9mcHVfY29udHJvbC5oIiAzCnR5cGVkZWYgdW5zaWduZWQg
aW50IGZwdV9jb250cm9sX3QgX19hdHRyaWJ1dGVfXyAoKF9fbW9kZV9fIChfX1NJX18pKSk7CiMg
NjUgIi91c3IvaW5jbHVkZS9mcHVfY29udHJvbC5oIiAzCmV4dGVybiBmcHVfY29udHJvbF90IF9f
ZnB1X2NvbnRyb2w7CiMgMTUgInRlc3QuY2MiIDIKCnZvaWQgZ2xpYmNfc2V0ZnB1Y3coIGZwdV9j
b250cm9sX3Qgc2V0ICkKewogICAgICAgIGZwdV9jb250cm9sX3QgY3c7CgoKICAgICAgICAoIHsg
dW5pb24geyBkb3VibGUgZDsgZnB1X2NvbnRyb2xfdCBjd1syXTsgfSB0bXAgX19hdHRyaWJ1dGVf
XygoX19hbGlnbmVkX18oOCkpKTsgX19hc21fXyAoIm1mZnMgMDsgc3RmZCVVMCAwLCUwIiA6ICI9
bSIgKHRtcC5kKSA6IDogImZyMCIpOyAoY3cpPXRtcC5jd1sxXTsgdG1wLmN3WzFdOyB9ICk7CgoK
CiAgICAgICAgY3cgJj0gMHhmZmZmZmYwMDsKICAgICAgICBjdyB8PSBzZXQgJiB+MHhmZmZmZmYw
MDsKCiAgICAgICAgeyB1bmlvbiB7IGRvdWJsZSBkOyBmcHVfY29udHJvbF90IGN3WzJdOyB9IHRt
cCBfX2F0dHJpYnV0ZV9fKChfX2FsaWduZWRfXyg4KSkpOyB0bXAuY3dbMF0gPSAweEZGRjgwMDAw
OyB0bXAuY3dbMV0gPSBjdzsgX19hc21fXyAoImxmZCVVMCAwLCUwOyBtdGZzZiAyNTUsMCIgOiA6
ICJtIiAodG1wLmQpIDogImZyMCIpOyB9Owp9Cg==


             reply	other threads:[~2002-05-20 18:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-20 11:16 Franz.Sirl-kernel [this message]
2002-06-20 13:16 rth
2002-06-20 16: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=20020520181157.12036.qmail@sources.redhat.com \
    --to=franz.sirl-kernel@lauterbach.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).