Linux-csky Archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: linux-riscv@lists.infradead.org, akpm@linux-foundation.org,
	arnd@arndb.de, linux-csky@vger.kernel.org,
	loongarch@lists.linux.dev, linux-mips@vger.kernel.org,
	linux-sh@vger.kernel.org, chris@zankel.net, jcmvbkbc@gmail.com,
	lkp@intel.com
Subject: Re: [PATCH] libgcc: Add forward declarations for generic library routines
Date: Mon, 08 May 2023 14:41:56 +0000	[thread overview]
Message-ID: <168355691617.25692.18413165340491314933.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <5cdbe08296693dd53849f199c3933e16e97b33c1.1682088593.git.geert+renesas@glider.be>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Andrew Morton <akpm@linux-foundation.org>:

On Fri, 21 Apr 2023 16:54:24 +0200 you wrote:
> With W=1 on platforms that use the generic gcc library routines
> (csky/loongarch/mips/riscv/sh/xtensa):
> 
>     lib/ashldi3.c:9:19: warning: no previous prototype for '__ashldi3' [-Wmissing-prototypes]
> 	9 | long long notrace __ashldi3(long long u, word_type b)
> 	  |                   ^~~~~~~~~
>       CC      lib/ashrdi3.o
>     lib/ashrdi3.c:9:19: warning: no previous prototype for '__ashrdi3' [-Wmissing-prototypes]
> 	9 | long long notrace __ashrdi3(long long u, word_type b)
> 	  |                   ^~~~~~~~~
>       CC      lib/cmpdi2.o
>     lib/cmpdi2.c:9:19: warning: no previous prototype for '__cmpdi2' [-Wmissing-prototypes]
> 	9 | word_type notrace __cmpdi2(long long a, long long b)
> 	  |                   ^~~~~~~~
>       CC      lib/lshrdi3.o
>     lib/lshrdi3.c:9:19: warning: no previous prototype for '__lshrdi3' [-Wmissing-prototypes]
> 	9 | long long notrace __lshrdi3(long long u, word_type b)
> 	  |                   ^~~~~~~~~
>       CC      lib/muldi3.o
>     lib/muldi3.c:49:19: warning: no previous prototype for '__muldi3' [-Wmissing-prototypes]
>        49 | long long notrace __muldi3(long long u, long long v)
> 	  |                   ^~~~~~~~
>       CC      lib/ucmpdi2.o
>     lib/ucmpdi2.c:8:19: warning: no previous prototype for '__ucmpdi2' [-Wmissing-prototypes]
> 	8 | word_type notrace __ucmpdi2(unsigned long long a, unsigned long long b)
> 	  |                   ^~~~~~~~~
> 
> [...]

Here is the summary with links:
  - libgcc: Add forward declarations for generic library routines
    https://git.kernel.org/riscv/c/4f20b7471c57

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-05-08 14:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-21 14:54 [PATCH] libgcc: Add forward declarations for generic library routines Geert Uytterhoeven
2023-04-21 20:38 ` Arnd Bergmann
2023-04-29 20:20   ` Palmer Dabbelt
2023-04-30 13:03     ` Geert Uytterhoeven
2023-05-08 14:41 ` patchwork-bot+linux-riscv [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=168355691617.25692.18413165340491314933.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=chris@zankel.net \
    --cc=geert+renesas@glider.be \
    --cc=jcmvbkbc@gmail.com \
    --cc=linux-csky@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=loongarch@lists.linux.dev \
    /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).