public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "arnez at linux dot ibm.com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug math/30130] New: [s390] The _FPU_SETCW macro yields compile error with Clang
Date: Thu, 16 Feb 2023 16:26:14 +0000	[thread overview]
Message-ID: <bug-30130-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=30130

            Bug ID: 30130
           Summary: [s390] The _FPU_SETCW macro yields compile error with
                    Clang
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: math
          Assignee: unassigned at sourceware dot org
          Reporter: arnez at linux dot ibm.com
  Target Milestone: ---

The _FPU_SETCW and _FPU_GETCW macros don't work with Clang.  Compiling this
sample program:

    #include <fpu_control.h>
    void foo() { _FPU_SETCW(0); }

gives

    foo.c:2:14: error: invalid operand for instruction
    void foo() { _FPU_SETCW(0); }
                 ^

This is because the inline assembly contains a spurious second operand which is
accepted by the GNU assembler, but not by Clang/LLVM.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2023-02-16 16:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 16:26 arnez at linux dot ibm.com [this message]
2023-02-16 16:28 ` [Bug math/30130] " arnez at linux dot ibm.com
2023-02-16 16:38 ` arnez at linux dot ibm.com
2023-02-28 12:21 ` stli at linux dot ibm.com
2023-02-28 13:05 ` stli at linux dot ibm.com

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=bug-30130-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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).