From: "H.J. Lu" <hjl.tools@gmail.com>
To: Alexander Monakov <amonakov@ispras.ru>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 1/2] gcc_qsort: source code changes
Date: Sun, 13 May 2018 23:56:00 -0000 [thread overview]
Message-ID: <CAMe9rOq+ieXOMsbmv2a6YDXpt-sxU_+p2PJXxqBKpwyiVO1XYQ@mail.gmail.com> (raw)
In-Reply-To: <20180510155641.2950-2-amonakov@ispras.ru>
On Thu, May 10, 2018 at 8:56 AM, Alexander Monakov <amonakov@ispras.ru> wrote:
> * sort.cc: New file.
> * system.h [!CHECKING_P] (qsort): Redirect to gcc_qsort.
> * vec.c (qsort_chk): Use gcc_qsort.
>
This breaks bootstrap on Fedora 28/i686:
https://gcc.gnu.org/ml/gcc-regression/2018-05/msg00088.html
../../src-trunk/gcc/sort.cc:112:5: note: in expansion of macro ‘REORDER_45’
REORDER_45 (8, 8, 0);
^~~~~~~~~~
../../src-trunk/gcc/sort.cc:100:10: error: ‘void* memcpy(void*, const
void*, size_t)’ forming offset [5, 8] is out of the bounds [0, 4] of
object ‘t2’ with type ‘size_t’ {aka ‘unsigned int’}
[-Werror=array-bounds]
memcpy (&t2, e2 + OFFSET, SIZE); \
~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~
../../src-trunk/gcc/sort.cc:112:5: note: in expansion of macro ‘REORDER_45’
REORDER_45 (8, 8, 0);
^~~~~~~~~~
../../src-trunk/gcc/sort.cc:97:18: note: ‘t2’ declared here
size_t t0, t1, t2, t3; \
^~
../../src-trunk/gcc/sort.cc:112:5: note: in expansion of macro ‘REORDER_45’
REORDER_45 (8, 8, 0);
^~~~~~~~~~
../../src-trunk/gcc/sort.cc:101:10: error: ‘void* memcpy(void*, const
void*, size_t)’ forming offset [5, 8] is out of the bounds [0, 4] of
object ‘t3’ with type ‘size_t’ {aka ‘unsigned int’}
[-Werror=array-bounds]
memcpy (&t3, e3 + OFFSET, SIZE); \
~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~
../../src-trunk/gcc/sort.cc:112:5: note: in expansion of macro ‘REORDER_45’
REORDER_45 (8, 8, 0);
^~~~~~~~~~
../../src-trunk/gcc/sort.cc:97:22: note: ‘t3’ declared here
size_t t0, t1, t2, t3; \
^~
../../src-trunk/gcc/sort.cc:112:5: note: in expansion of macro ‘REORDER_45’
REORDER_45 (8, 8, 0);
^~~~~~~~~~
../../src-trunk/gcc/sort.cc:105:10: error: ‘void* memcpy(void*, const
void*, size_t)’ forming offset [5, 8] is out of the bounds [0, 4] of
object ‘t0’ with type ‘size_t’ {aka ‘unsigned int’}
[-Werror=array-bounds]
memcpy (out, &t0, SIZE); out += STRIDE; \
~~~~~~~^~~~~~~~~~~~~~~~
../../src-trunk/gcc/sort.cc:112:5: note: in expansion of macro ‘REORDER_45’
REORDER_45 (8, 8, 0);
^~~~~~~~~~
../../src-trunk/gcc/sort.cc:97:10: note: ‘t0’ declared here
size_t t0, t1, t2, t3; \
^~
../../src-trunk/gcc/sort.cc:112:5: note: in expansion of macro ‘REORDER_45’
REORDER_45 (8, 8, 0);
^~~~~~~~~~
../../src-trunk/gcc/sort.cc:106:10: error: ‘void* memcpy(void*, const
void*, size_t)’ forming offset [5, 8] is out of the bounds [0, 4] of
object ‘t1’ with type ‘size_t’ {aka ‘unsigned int’}
[-Werror=array-bounds]
memcpy (out, &t1, SIZE); out += STRIDE; \
~~~~~~~^~~~~~~~~~~~~~~~
../../src-trunk/gcc/sort.cc:112:5: note: in expansion of macro ‘REORDER_45’
REORDER_45 (8, 8, 0);
^~~~~~~~~~
../../src-trunk/gcc/sort.cc:97:14: note: ‘t1’ declared here
size_t t0, t1, t2, t3; \
^~
../../src-trunk/gcc/sort.cc:112:5: note: in expansion of macro ‘REORDER_45’
REORDER_45 (8, 8, 0);
^~~~~~~~~~
../../src-trunk/gcc/sort.cc:107:10: error: ‘void* memcpy(void*, const
void*, size_t)’ forming offset [5, 8] is out of the bounds [0, 4] of
object ‘t2’ with type ‘size_t’ {aka ‘unsigned int’}
[-Werror=array-bounds]
memcpy (out, &t2, SIZE); out += STRIDE; \
~~~~~~~^~~~~~~~~~~~~~~~
../../src-trunk/gcc/sort.cc:112:5: note: in expansion of macro ‘REORDER_45’
REORDER_45 (8, 8, 0);
^~~~~~~~~~
../../src-trunk/gcc/sort.cc:97:18: note: ‘t2’ declared here
size_t t0, t1, t2, t3; \
^~
../../src-trunk/gcc/sort.cc:112:5: note: in expansion of macro ‘REORDER_45’
REORDER_45 (8, 8, 0);
^~~~~~~~~~
../../src-trunk/gcc/sort.cc:108:10: error: ‘void* memcpy(void*, const
void*, size_t)’ forming offset [5, 8] is out of the bounds [0, 4] of
object ‘t3’ with type ‘size_t’ {aka ‘unsigned int’}
[-Werror=array-bounds]
memcpy (out, &t3, SIZE); \
~~~~~~~^~~~~~~~~~~~~~~~
../../src-trunk/gcc/sort.cc:112:5: note: in expansion of macro ‘REORDER_45’
REORDER_45 (8, 8, 0);
^~~~~~~~~~
../../src-trunk/gcc/sort.cc:97:22: note: ‘t3’ declared here
size_t t0, t1, t2, t3; \
^~
../../src-trunk/gcc/sort.cc:112:5: note: in expansion of macro ‘REORDER_45’
REORDER_45 (8, 8, 0);
^~~~~~~~~~
next prev parent reply other threads:[~2018-05-13 23:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 15:57 [PATCH 0/2] Introduce gcc_qsort Alexander Monakov
2018-05-10 15:57 ` [PATCH 2/2] gcc_qsort: build system changes Alexander Monakov
2018-05-11 9:32 ` Richard Biener
2018-05-10 17:01 ` [PATCH 1/2] gcc_qsort: source code changes Alexander Monakov
2018-05-10 17:01 ` David Malcolm
2018-05-10 17:44 ` Richard Biener
2018-05-10 18:08 ` Alexander Monakov
2018-05-10 18:57 ` DJ Delorie
2018-05-11 12:03 ` Richard Biener
2018-05-11 13:12 ` Alexander Monakov
2018-05-13 23:56 ` H.J. Lu [this message]
2018-05-14 8:44 ` Alexander Monakov
2018-05-14 9:08 ` Richard Biener
2018-05-10 17:35 ` [PATCH 0/2] Introduce gcc_qsort Jakub Jelinek
2018-05-10 17:48 ` Alexander Monakov
2018-05-10 17:43 ` Richard Biener
2018-05-10 17:57 ` Alexander Monakov
2018-05-11 10:35 ` Segher Boessenkool
2018-05-11 10:44 ` Alexander Monakov
2018-05-11 12:00 ` Segher Boessenkool
2018-05-11 12:16 ` Alexander Monakov
2018-05-11 12:52 ` Segher Boessenkool
2018-05-11 16:54 ` Eric Botcazou
2018-05-11 11:17 ` Jakub Jelinek
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=CAMe9rOq+ieXOMsbmv2a6YDXpt-sxU_+p2PJXxqBKpwyiVO1XYQ@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=amonakov@ispras.ru \
--cc=gcc-patches@gcc.gnu.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).