public inbox for linux-sound@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: songxiebing <songxiebing@kylinos.cn>
Cc: tiwai@suse.com, perex@perex.cz, linux-sound@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v2] ALSA: core/seq: Optimize the return logic in cc_ev_to_ump_midi2
Date: Fri, 27 Mar 2026 12:43:09 +0100	[thread overview]
Message-ID: <87pl4pqz02.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260325015119.175835-1-songxiebing@kylinos.cn>

On Wed, 25 Mar 2026 02:51:19 +0100,
songxiebing wrote:
> 
> There are multiple early return branches within the func, and compiler
> optimizations(such as -O2/-O3)lead to abnormal stack frame analysis -
> objtool cannot comfirm that the stack frames of all branches can be
> correctly restored, thus generating false warnings.
> 
> Below:
> >> sound/core/seq/seq_ump_convert.o: warning: objtool: cc_ev_to_ump_midi2+0x589: return with modified stack frame
> 
> So we modify it by uniformly returning at the and of the function.
> 
> Signed-off-by: songxiebing <songxiebing@kylinos.cn>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202503200535.J3hAvcjw-lkp@intel.com/
> ---
> v2:
> - fix warning: this statement may fall through [-Wimplicit-fallthrough=]

Basically I don't like to take this kind of change just because a
stupid compiler can't handle it well.  But this particular code change
itself is simple enough, so maybe still worth to take.

Applied to for-next branch now.  Thanks.


Takashi

      reply	other threads:[~2026-03-27 11:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23  2:47 [PATCH] ALSA: core/seq: Optimize the return logic in cc_ev_to_ump_midi2 songxiebing
2026-03-24  1:40 ` kernel test robot
2026-03-24  4:20 ` kernel test robot
2026-03-24  7:35 ` kernel test robot
2026-03-25  1:51 ` [PATCH v2] " songxiebing
2026-03-27 11:43   ` Takashi Iwai [this message]

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=87pl4pqz02.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=perex@perex.cz \
    --cc=songxiebing@kylinos.cn \
    --cc=tiwai@suse.com \
    /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