This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: divdi3: incomplete fix in db3d848e154b?

From: Andreas Schwab <schwab at suse dot de>
To: Jeff Law <law at redhat dot com>
Cc: Adhemerval Zanella <adhemerval dot zanella at linaro dot org>, Alexey Neyman <stilor at att dot net>, libc-alpha at sourceware dot org
Date: Mon, 15 May 2017 17:17:36 +0200
Subject: Re: divdi3: incomplete fix in db3d848e154b?
Authentication-results: sourceware.org; auth=none
References: <e99d6df7-8cb2-282d-ffeb-fcc383db94be@att.net> <5055b77a-a49d-3cc8-8325-58ef5cad23bf@linaro.org> <964c0241-3210-b36c-2e3a-3a7c5ce931a4@redhat.com>

On Mai 15 2017, Jeff Law <law@redhat.com> wrote:

> I certainly understand Carlos's position, even if I don't 100% agree with
> it (particularly from a security standpoint).  However, given that
> position, building all glibc targets with -fno-isolate-erroneous-paths
> would seem to be the right thing to do.

libgcc2.c has the same problem.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

References:
- divdi3: incomplete fix in db3d848e154b?
  - From: Alexey Neyman
- Re: divdi3: incomplete fix in db3d848e154b?
  - From: Adhemerval Zanella
- Re: divdi3: incomplete fix in db3d848e154b?
  - From: Jeff Law

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]