public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jon@mast.queensu.ca
To: gcc-gnats@gcc.gnu.org
Subject: inline-asm/9981: attempt to read 64 bit pentium timestamp failure
Date: Thu, 06 Mar 2003 15:36:00 -0000	[thread overview]
Message-ID: <20030306153234.19478.qmail@sources.redhat.com> (raw)


>Number:         9981
>Category:       inline-asm
>Synopsis:       attempt to read 64 bit pentium timestamp failure
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Mar 06 15:36:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     jon@mast.queensu.ca
>Release:        gcc 3.2
>Organization:
>Environment:

>Description:
Inline assembly to read 64 bit pentium timer fails with

testrdtsc.c:7: can't find a register in class `AD_REGS' while reloading `asm'

under gcc 3.2 . The info seems to indicate =A constraint allows a 64 bit result.
>How-To-Repeat:
gcc -g -O6 -o testrdtsc testrdtsc.c
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="testrdtsc.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="testrdtsc.c"

Lyogc3VwcG9ydCBmb3IgcGVudGl1bSBjeWNsZSBjb3VudGVyICovCgpzdGF0aWMgX19pbmxpbmVf
XyB1bnNpZ25lZCBsb25nIGxvbmcgaW50IHJkdHNjKCkKewogIHVuc2lnbmVkIGxvbmcgbG9uZyBp
bnQgeDsKCiAgYXNtIF9fdm9sYXRpbGVfXyAoCiAgICAgICAgICAgICAgICAgICAgIi5ieXRlIDB4
MGYsIDB4MzEiCiAgICAgICAgICAgICAgICAgICAgOiAiPUEiICh4KQogICAgICAgICAgICAgICAg
ICAgIDoKICAgICAgICAgICAgICAgICAgICA6ICIlZWF4IiwgIiVlZHgiCiAgICAgICAgICAgICAg
ICAgICAgKTsKICByZXR1cm4oeCk7Cn0KIAppbnQgbWFpbihpbnQgYXJnYywgY2hhciAqKmFyZ3Yp
CnsKICBwcmluZigicmR0c2MgcmV0dXJuZWQgJWQiLCByZHRzYygpKTsKICByZXR1cm4gMDsKICAK
fQoK


             reply	other threads:[~2003-03-06 15:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-06 15:36 jon [this message]
2003-05-10 21:06 Dara Hazeghi

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=20030306153234.19478.qmail@sources.redhat.com \
    --to=jon@mast.queensu.ca \
    --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).