linux-kernel - objtool failures with -march=atom

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAK8P3a2X3frpKJYf8+RqUFv355WJTYtRcb2EEjp7MLCt3SsD4g@mail.gmail.com>
Date:   Wed, 26 Jul 2017 12:12:04 +0200
From:   Arnd Bergmann <arnd@...db.de>
To:     Josh Poimboeuf <jpoimboe@...hat.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Ingo Molnar <mingo@...nel.org>
Subject: objtool failures with -march=atom

With the latest objtool failure, I get countless warnings when
-march=atom or -mtune=atom is used,
at least with gcc-4.9 through gcc-7 (I did not try older versions:

kernel/sched/core.o: warning: objtool:
trace_raw_output_sched_stat_runtime()+0x9a: return with modified stack
frame
kernel/sched/core.o: warning: objtool: cpu_cgroup_fork()+0x7c: return
with modified stack frame
kernel/sched/core.o: warning: objtool: walk_tg_tree_from()+0xd3:
return with modified stack frame
kernel/sched/core.o: warning: objtool: ttwu_do_wakeup()+0x2a8: return
with modified stack frame
kernel/sched/core.o: warning: objtool: do_set_cpus_allowed()+0x1fe:
return with modified stack frame
kernel/sched/core.o: warning: objtool: sched_ttwu_pending()+0xf2:
return with modified stack frame
kernel/sched/core.o: warning: objtool: sched_exec()+0xd0: return with
modified stack frame
kernel/sched/core.o: warning: objtool: task_sched_runtime()+0x148:
return with modified stack frame
kernel/sched/core.o: warning: objtool: sched_move_task()+0x176: return
with modified stack frame
kernel/sched/core.o: warning: objtool: sched_init()+0x6cb: return with
modified stack frame

Can you have a look?

There are probably other failures as well, I'm trying to reproduce the
others now with atom
optimizations disabled.

        Arnd