public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: vladimir.kondratiev@intel.com To: gcc-gnats@gcc.gnu.org Subject: c++/3604: g++ can't compile specific inline asm with -O Date: Sat, 07 Jul 2001 14:06:00 -0000 [thread overview] Message-ID: <20010707205836.15338.qmail@sourceware.cygnus.com> (raw) >Number: 3604 >Category: c++ >Synopsis: g++ can't compile specific inline asm with -O >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Sat Jul 07 14:06:00 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Vladimir Kondratiev >Release: 3.0 >Organization: >Environment: []gcc -v Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.0/specs Configured with: ../configure --prefix=/usr Thread model: single gcc version 3.0 []uname -mrs Linux 2.4.5-10 i686 >Description: File attached fails to compile as c++ code with optimization. Errors produced: convert.cc: In function `long int f(float)': convert.cc:4: output number 0 not directly addressable convert.cc:4: inconsistent operand constraints in an `asm' This file do compiles, however, without optimization. It compiles as 'C' code with any optimization. Original code is extracted from KDE libs. >How-To-Repeat: Not compiled: gcc -O -c convert.cc (as well as -O1, -O2, -O3)Do compiled: gcc -c convert.cc gcc -x c -O3 convert.cc (as C code it compiles with any optimization) >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="convert.cc" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="convert.cc" bG9uZyBmIChmbG9hdCBpbnZhbCkKewogIGxvbmcgcmV0OwogIGFzbSAoImZpc3RwbCAlMCIgOiAi PW0iIChyZXQpIDogInQiIChpbnZhbCkgOiAic3QiKTsKICByZXR1cm4gcmV0Owp9Cgo=
next reply other threads:[~2001-07-07 14:06 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-07-07 14:06 vladimir.kondratiev [this message] 2001-07-11 10:31 mmitchel
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=20010707205836.15338.qmail@sourceware.cygnus.com \ --to=vladimir.kondratiev@intel.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: linkBe 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).