public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-libs/plib/
Date: Wed, 28 Feb 2024 22:57:16 +0000 (UTC)	[thread overview]
Message-ID: <1709161021.aec66421746a0ac2dc2b2eebed6e0f0d2abe3405.sam@gentoo> (raw)

commit:     aec66421746a0ac2dc2b2eebed6e0f0d2abe3405
Author:     Eli Schwartz <eschwartz93 <AT> gmail <DOT> com>
AuthorDate: Wed Feb 28 22:30:22 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Feb 28 22:57:01 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=aec66421

media-libs/plib: mark LTO-unsafe, mark strict-aliasing unsafe

This code is formally terrible. It is so terrible, because upstream
claims: "PLIB has been obsolete and unmaintained for at LEAST 15
years!!"

https://sourceforge.net/p/plib/bugs/55/#88e9

And that was already 3 years ago. We can't fix it so limit the extent to
which compilers are allowed to misinterpret it.

Closes: https://bugs.gentoo.org/860048
Signed-off-by: Eli Schwartz <eschwartz93 <AT> gmail.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>

 media-libs/plib/plib-1.8.5-r4.ebuild | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/media-libs/plib/plib-1.8.5-r4.ebuild b/media-libs/plib/plib-1.8.5-r4.ebuild
index 3e4494514020..b5769bd1ab11 100644
--- a/media-libs/plib/plib-1.8.5-r4.ebuild
+++ b/media-libs/plib/plib-1.8.5-r4.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2023 Gentoo Authors
+# Copyright 1999-2024 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=8
@@ -32,6 +32,12 @@ src_prepare() {
 src_configure() {
 	append-cxxflags -std=c++03
 
+	# violates strict aliasing rules and is LTO-unsafe: https://bugs.gentoo.org/860048
+	# Per upstream in 2021, "PLIB has been obsolete and unmaintained for at LEAST 15 years!!"
+	# so this is getting fixed exactly never and getting worse.
+	append-cxxflags -fno-strict-aliasing
+	filter-lto
+
 	local myconf=(
 		--enable-shared
 	)


             reply	other threads:[~2024-02-28 22:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-28 22:57 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-02 20:28 [gentoo-commits] repo/gentoo:master commit in: media-libs/plib/ James Le Cuirot
2023-05-11  1:21 Sam James
2022-09-09  7:59 David Seifert
2021-09-22 22:26 Ionen Wolkens
2021-05-31  6:09 Agostino Sarubbo
2021-05-28  0:29 Sam James
2021-05-28  0:29 Sam James
2021-05-28  0:29 Sam James
2020-12-02  0:32 Aaron Bauman
2020-10-03  9:16 Sergei Trofimovich
2020-10-01 23:06 Sergei Trofimovich
2020-09-29 21:25 Sergei Trofimovich
2016-03-19 15:34 Michael Sterrett
2016-03-14 18:43 Tobias Klausmann
2016-03-09  4:26 Jeroen Roovers
2016-03-02 14:22 Agostino Sarubbo

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=1709161021.aec66421746a0ac2dc2b2eebed6e0f0d2abe3405.sam@gentoo \
    --to=sam@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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