public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "simon.chopin at canonical dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug math/30909] New: aarch64: using intrinsic vector types in math-vector.h breaks C-parsing tools
Date: Wed, 27 Sep 2023 11:30:44 +0000	[thread overview]
Message-ID: <bug-30909-131@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 30909
           Summary: aarch64: using intrinsic vector types in math-vector.h
                    breaks C-parsing tools
           Product: glibc
           Version: 2.38
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: math
          Assignee: unassigned at sourceware dot org
          Reporter: simon.chopin at canonical dot com
  Target Milestone: ---

The use of vector types such as __Float32x4_t in the aarch64 math-vector.h
header breaks quite a few programs that are essentially parsing C code but
using GCC as their preprocessor. GCC expands to the paths using its own
intrinsic types, which aren't implemented by the consuming programs.

I'm not sure if this qualifies as a bug in glibc, as it seems reasonable to
rely on those types, but we've seen this happen in quite a few instances in
Ubuntu:

https://bugs.launchpad.net/ubuntu/+source/mumax3/+bug/2032624

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

             reply	other threads:[~2023-09-27 11:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27 11:30 simon.chopin at canonical dot com [this message]
2023-09-27 14:28 ` [Bug math/30909] " simon.chopin at canonical dot com
2023-11-02 13:41 ` connor.baker at tweag dot io
2024-05-06 20:23 ` aurelien at aurel32 dot net

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-30909-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).