On Tue, 1 Sep 2020, Jeff Law via Gcc-patches wrote:
> > With this commit:
> > https://gcc.gnu.org/pipermail/gcc-patches/2020-September/553109.html
> > the remaining failures should now be gone. Please let me know if
> > any persist.
> There's a related glibc build failure, but I think Joseph ack'
On 9/1/20 4:22 PM, Jeff Law wrote:
On Tue, 2020-09-01 at 16:13 -0600, Martin Sebor wrote:
On 9/1/20 2:09 AM, Christophe Lyon wrote:
On Mon, 31 Aug 2020 at 23:50, Martin Sebor wrote:
On 8/31/20 4:51 AM, Christophe Lyon wrote:
Hi,
...
I pushed a small aarch64 patch as obvious:
2020-0
On Tue, 2020-09-01 at 16:13 -0600, Martin Sebor wrote:
> On 9/1/20 2:09 AM, Christophe Lyon wrote:
> > On Mon, 31 Aug 2020 at 23:50, Martin Sebor wrote:
> > > On 8/31/20 4:51 AM, Christophe Lyon wrote:
> > > > Hi,
> > > >
> > > ...
> > > > I pushed a small aarch64 patch as obvious:
> > > >
On 9/1/20 2:09 AM, Christophe Lyon wrote:
On Mon, 31 Aug 2020 at 23:50, Martin Sebor wrote:
On 8/31/20 4:51 AM, Christophe Lyon wrote:
Hi,
...
I pushed a small aarch64 patch as obvious:
2020-08-31 Christophe Lyon
gcc/testsuite/
* gcc.target/aarch64/strcmpopt_
On Mon, 31 Aug 2020 at 23:50, Martin Sebor wrote:
>
> On 8/31/20 4:51 AM, Christophe Lyon wrote:
> > Hi,
> >
> ...
> >
> > I pushed a small aarch64 patch as obvious:
> > 2020-08-31 Christophe Lyon
> >
> > gcc/testsuite/
> > * gcc.target/aarch64/strcmpopt_6.c: Suppress -Ws
On 8/31/20 3:50 PM, Martin Sebor wrote:
On 8/31/20 4:51 AM, Christophe Lyon wrote:
Hi,
...
I pushed a small aarch64 patch as obvious:
2020-08-31 Christophe Lyon
gcc/testsuite/
* gcc.target/aarch64/strcmpopt_6.c: Suppress
-Wstringop-overread.
(same as you added fo
On 8/31/20 4:51 AM, Christophe Lyon wrote:
Hi,
...
I pushed a small aarch64 patch as obvious:
2020-08-31 Christophe Lyon
gcc/testsuite/
* gcc.target/aarch64/strcmpopt_6.c: Suppress -Wstringop-overread.
(same as you added for i386)
Thank you!
On arm, there is a
Hi,
On Wed, 26 Aug 2020 at 22:36, Jeff Law via Gcc-patches
wrote:
>
> On Tue, 2020-06-23 at 20:05 -0600, Martin Sebor wrote:
> > -Wstringop-overflow is issued for both writing and reading past
> > the end, even though the latter problem is often viewed as being
> > lower severity than the former,
On Tue, 2020-06-23 at 20:05 -0600, Martin Sebor wrote:
> -Wstringop-overflow is issued for both writing and reading past
> the end, even though the latter problem is often viewed as being
> lower severity than the former, or at least sufficiently different
> to triage separately. In CWE, for examp
Ping: https://gcc.gnu.org/pipermail/gcc-patches/2020-June/548786.html
On 8/10/20 10:48 AM, Martin Sebor wrote:
Ping: https://gcc.gnu.org/pipermail/gcc-patches/2020-June/548786.html
On 7/26/20 11:42 AM, Martin Sebor wrote:
Ping: https://gcc.gnu.org/pipermail/gcc-patches/2020-June/548786.html
O
Ping: https://gcc.gnu.org/pipermail/gcc-patches/2020-June/548786.html
On 7/26/20 11:42 AM, Martin Sebor wrote:
Ping: https://gcc.gnu.org/pipermail/gcc-patches/2020-June/548786.html
On 7/13/20 6:05 PM, Martin Sebor wrote:
Ping: https://gcc.gnu.org/pipermail/gcc-patches/2020-June/548786.html
On
Ping: https://gcc.gnu.org/pipermail/gcc-patches/2020-June/548786.html
On 7/13/20 6:05 PM, Martin Sebor wrote:
Ping: https://gcc.gnu.org/pipermail/gcc-patches/2020-June/548786.html
On 7/7/20 12:56 PM, Martin Sebor wrote:
Ping. Despite its size, there isn't much new in the patch, it
pretty much
Ping: https://gcc.gnu.org/pipermail/gcc-patches/2020-June/548786.html
On 7/7/20 12:56 PM, Martin Sebor wrote:
Ping. Despite its size, there isn't much new in the patch, it
pretty much just splits an existing warning into two, one for
buffer overflow and another for "overread."
https://gcc.gnu.
Ping. Despite its size, there isn't much new in the patch, it
pretty much just splits an existing warning into two, one for
buffer overflow and another for "overread."
https://gcc.gnu.org/pipermail/gcc-patches/2020-June/548786.html
On 6/23/20 8:05 PM, Martin Sebor wrote:
-Wstringop-overflow is
14 matches
Mail list logo
