From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/30465] New: flang fails self compare on f38
Date: Thu, 18 May 2023 22:13:35 +0000 [thread overview]
Message-ID: <bug-30465-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30465
Bug ID: 30465
Summary: flang fails self compare on f38
Product: libabigail
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: woodard at redhat dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
fedabipkgdiff --self-compare -a --from fc38 flang
Comparing the ABI of binaries between flang-16.0.3-1.fc38.x86_64.rpm and
flang-16.0.3-1.fc38.x86_64.rpm:
==== SELF CHECK SUCCEEDED for 'libFIRTransforms.so.16' ====
==== SELF CHECK SUCCEEDED for 'bbc' ====
================ changes of 'libFortranEvaluate.so.16'===============
Functions changes summary: 0 Removed, 0 Changed, 0 Added function
Variables changes summary: 0 Removed, 0 Changed (5 filtered out), 0 Added
variables
================ end of changes of 'libFortranEvaluate.so.16'===============
================ changes of 'libFortranLower.so.16'===============
Functions changes summary: 0 Removed, 0 Changed, 0 Added function
Variables changes summary: 0 Removed, 0 Changed (34 filtered out), 0 Added
variables
================ end of changes of 'libFortranLower.so.16'===============
With libabigail trunk as of:
commit 06e8d54d0404ccf2a103804ec568797822152b69 (HEAD -> master, origin/master,
origin/HEAD)
Author: Dodji Seketeli <dodji@redhat.com>
Date: Wed May 17 13:44:58 2023 +0200
Bug 29693 - clang-libs from f37 fails self test
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-05-18 22:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 22:13 woodard at redhat dot com [this message]
2023-05-18 22:13 ` [Bug default/30465] " woodard at redhat dot 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-30465-9487@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libabigail@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).