https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99828
--- Comment #16 from Martin Liška ---
(In reply to andi from comment #15)
> > Provided I cannot reproduce on the current kernel, where exactly does this
> > come
> > from?
>
> Usually I had to do a longer loop of randconfig builds to find it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99828
--- Comment #15 from andi at firstfloor dot org ---
> Provided I cannot reproduce on the current kernel, where exactly does this
> come
> from?
Usually I had to do a longer loop of randconfig builds to find it. It only
happens in some specific
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99828
--- Comment #14 from Jiri Slaby ---
(In reply to Richard Biener from comment #13)
> The testcase still does not work on master or with 12.2, thus reconfirmed.
Hmm:
(In reply to Martin Liška from comment #0)
> Noticed by Andi Kleen in kernel,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99828
Richard Biener changed:
What|Removed |Added
Known to fail||12.2.0
Last reconfirmed|2021-03-30
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99828
--- Comment #12 from Jiri Slaby ---
(In reply to Jiri Slaby from comment #11)
> Looking at the kernel patch, it says:
> This is fixed now in gcc, but work around it on older compilers
> by using a wrapper.
>
> If so, how was this fixed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99828
Jiri Slaby changed:
What|Removed |Added
CC||jirislaby at gmail dot com
--- Comment #11
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99828
--- Comment #10 from Martin Liška ---
> ?? obviously bad reduction.
Fixed with:
$ cat 3.i
enum { false, true } * __memcpy();
_Bool kasan_check_range();
void *memcpy(void *dest, void *src, long len) {
if (kasan_check_range(len, false, 0) ||
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99828
--- Comment #9 from rguenther at suse dot de ---
On Wed, 31 Mar 2021, marxin at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99828
>
> --- Comment #8 from Martin Liška ---
> All right, I vanished the test-case:
>
> $
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99828
--- Comment #8 from Martin Liška ---
All right, I vanished the test-case:
$ cat 1.i
inline __attribute__((__always_inline__)) __attribute__((gnu_inline)) void *
memcpy();
void *apply_relocate_add_write = memcpy;
$ touch 2.s
$ cat 3.i
enum {
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99828
--- Comment #7 from Jan Hubicka ---
> Yeah, and then maybe diagnose this "ODR violation". Still
I think we do have this kinds of divergence (like glibcs
fortification), so I am not sure we want to warn by default.
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99828
--- Comment #6 from Richard Biener ---
(In reply to Jan Hubicka from comment #5)
> > Btw, one solution would be to drop __always_inline__ after always-inline
> > inlining
> > and thus make it reliably not present for IPA inlining.
> Removing it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99828
--- Comment #5 from Jan Hubicka ---
> Btw, one solution would be to drop __always_inline__ after always-inline
> inlining
> and thus make it reliably not present for IPA inlining.
Removing it would make you to lose those errors, but we can
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99828
--- Comment #4 from rguenther at suse dot de ---
On March 30, 2021 7:44:56 PM GMT+02:00, andi-gcc at firstfloor dot org
wrote:
>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99828
>
>--- Comment #3 from Andi Kleen ---
>So what do you want to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99828
--- Comment #3 from Andi Kleen ---
So what do you want to fix in the kernel?
Use a wrapper for taking the address of the memcpy?
(I hope nothing in gcc would remove such a wrapper)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99828
Richard Biener changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99828
Richard Biener changed:
What|Removed |Added
Keywords||diagnostic,
|
16 matches
Mail list logo
