From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 09AA7396ECB3; Wed, 27 May 2020 13:48:05 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 09AA7396ECB3 From: "carlos at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug math/26052] Wine position issues with recent glibc versions and gcc 10 Date: Wed, 27 May 2020 13:48:04 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: math X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: carlos at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc resolution bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: glibc-bugs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Glibc-bugs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2020 13:48:05 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D26052 Carlos O'Donell changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |carlos at redhat dot com Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #2 from Carlos O'Donell --- I appreciate the bug report, but this isn't enough information to pin-point= the issue, a distribution has a lot of moving parts. Before we can act on a rep= ort like this we need a much narrower reproducer. To get hat narrow reproducer = we rely on distribution maintainers, like those working in the Arch Linux proj= ect to supply those details. I suggest you start with your distribution built binaries and interact with= the Arch Linux maintainers and change one piece of software at a time and make = sure that the result is exactly as you expect. When you find a failure you need = to narrow it down to an exact component and an exact change. We, the glibc maintainres, need more reduced examples where behaviour chang= e is clearly restricted to the component in question e.g. glibc, or even gcc, and ld, which we deal with on a daily basis and which are part of the GNU Toolchain. I suggest opening a bug with Arch Linux, but make sure you start by using a= ll of their components and make sure you can reproduce the issue only with a s= mall change. I'm marking this bug RESOLVED/INVALID. --=20 You are receiving this mail because: You are on the CC list for the bug.=