Hi Michael,
Here is the link to the bug raised on launchpad.
https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1628207
On 09/23/2016 09:45 AM, Akshay Adiga wrote:
Hi Michael,
Anton found this bug and raised it against gcc v7.0 and a fix is
available
in upstream gcc.
https://gcc.gnu
Hi Michael,
Anton found this bug and raised it against gcc v7.0 and a fix is available
in upstream gcc.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71709
Currently, gcc v5.4.0 and v6.1.1 shipped with Ubuntu 16.04 and 16.10
respectively,
are hitting this problem.
I have also raise
Hi,
> But I can't merge that patch.
>
> Our options are one or both of:
> - get GCC fixed and backport the fix to the compilers we care about.
> - blacklist the broken compiler versions.
>
> Is there a GCC bug filed for this?
Likely: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71709
We need
Akshay Adiga writes:
> Observed that boot arguments (passed as CONFIG_CMDLINE) are not being
> picked up by kernel while using gcc-ppc64-linux-gnu v5.4.0 and v6.1.1.
> While it works as expected with v5.3.1 .
>
> Found that in init/main.c in setup_command_line() the pointers passed to
> strcpy(
Observed that boot arguments (passed as CONFIG_CMDLINE) are not being
picked up by kernel while using gcc-ppc64-linux-gnu v5.4.0 and v6.1.1.
While it works as expected with v5.3.1 .
Found that in init/main.c in setup_command_line() the pointers passed to
strcpy() is messed up.
source for setup_
5 matches
Mail list logo