public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: fmfkrauss@mindspring.com
To: gcc-gnats@gcc.gnu.org
Subject: preprocessor/6339: Problem with assembling the LDMXCSR instruction
Date: Wed, 17 Apr 2002 10:46:00 -0000	[thread overview]
Message-ID: <20020417174054.15299.qmail@sources.redhat.com> (raw)


>Number:         6339
>Category:       preprocessor
>Synopsis:       Problem with assembling the LDMXCSR instruction
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Wed Apr 17 10:46:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Frank Krauss
>Release:        gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release)
>Organization:
>Environment:
Hardware
   Pentium-4 P.C.
   Chipset - Intel 850
   Ram     - 256 Mb.
Software
   Distribution     - Caldera 2.3
   Kernel           - 2.4.18
   Processor family - Pentium-4
   Binutils         - 2.11.2
   GCC              - egcs-2.91.66
   AS               - GNU assembler 2.11.2	  
>Description:
Output of executing the following command:-
gcc ldmxcsr.s
    ldmxcsr.s: Assembler messages:
    ldmxcsr.s:1: Error: no such 386 instruction: 'ldmxcsr'
>How-To-Repeat:
Data is a one line file called <anything.s> with the
      following line in it:-
   ldmxcsr -4(%ebp)
>Fix:
If you pass the same one line file through the AS program
directly, it assembles fine.
I had to assemble the program that used this instruction
with the -S option to stop after the Assembler creation
step.
Then I had to pass the output throught the AS Assembler to
create the output module.
I then had to <kluge> the Makefile to bypass assembling this
program.
>Release-Note:
>Audit-Trail:
>Unformatted:


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

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20020417174054.15299.qmail@sources.redhat.com \
    --to=fmfkrauss@mindspring.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).