Nathan Chancellor writes:
>> >> And maybe request a similar llvm directory under pub/tools to make it
>> >> more official? :)
>
> We now have https://kernel.org/pub/tools/llvm/, which is about as
> official as we can get I suppose :)
Nice, thanks. Bookmarked and I'll advertise this to wireless d
On Fri, Mar 24, 2023 at 05:23:12PM +0200, Kalle Valo wrote:
> Nathan Chancellor writes:
>
> >> This is nitpicking but it would be nice if the tarball contents wouldn't
> >> conflict with each other. Now both llvm-16.0.0-aarch64.tar.gz and
> >> llvm-16.0.0-x86_64.tar extract to the same directory
Jani Nikula writes:
> On Sat, 25 Mar 2023, Masahiro Yamada wrote:
>
>> On Thu, Mar 23, 2023 at 1:56 AM Linus Torvalds
>> wrote:
>>>
>>> On Wed, Mar 22, 2023 at 9:40 AM Sedat Dilek wrote:
>>> >
>>> > You have to pass `make LLVM=1` in any case... to `oldconfig` or when
>>> > adding any MAKEFLAGS
On Sat, 25 Mar 2023, Masahiro Yamada wrote:
> Hello Linus,
>
>
> Thanks for giving me some more homeworks.
>
>
> On Thu, Mar 23, 2023 at 1:56 AM Linus Torvalds
> wrote:
>>
>> On Wed, Mar 22, 2023 at 9:40 AM Sedat Dilek wrote:
>> >
>> > You have to pass `make LLVM=1` in any case... to `oldconfig`
Hello Linus,
Thanks for giving me some more homeworks.
On Thu, Mar 23, 2023 at 1:56 AM Linus Torvalds
wrote:
>
> On Wed, Mar 22, 2023 at 9:40 AM Sedat Dilek wrote:
> >
> > You have to pass `make LLVM=1` in any case... to `oldconfig` or when
> > adding any MAKEFLAGS like -j${number-of-availabl
Nathan Chancellor writes:
>> This is nitpicking but it would be nice if the tarball contents wouldn't
>> conflict with each other. Now both llvm-16.0.0-aarch64.tar.gz and
>> llvm-16.0.0-x86_64.tar extract to the same directory llvm-16.0.0 with
>> same binary names. It would be much better if they
On Fri, Mar 24, 2023 at 12:54:01PM +0200, Kalle Valo wrote:
> Nathan Chancellor writes:
>
> > On Wed, Mar 22, 2023 at 02:44:47PM +0200, Kalle Valo wrote:
> >> Nathan Chancellor writes:
> >>
> >> > Perhaps these would make doing allmodconfig builds with clang more
> >> > frequently less painful
Nathan Chancellor writes:
> On Wed, Mar 22, 2023 at 02:44:47PM +0200, Kalle Valo wrote:
>> Nathan Chancellor writes:
>>
>> > Perhaps these would make doing allmodconfig builds with clang more
>> > frequently less painful for you?
>> >
>> > https://lore.kernel.org/llvm/20230319235619.GA18547@dev
On Mon, 20 Mar 2023 at 19:05, Nathan Chancellor wrote:
>
> On Sun, Mar 19, 2023 at 01:50:21PM -0700, Linus Torvalds wrote:
> > So rc3 is fairly big, but that's not hugely usual: it's when a lot of
> > the fixes tick up as it takes a while before people find and start
> > reporting issues.
>
> ...
On Wed, Mar 22, 2023 at 09:36:37AM -0700, Nathan Chancellor wrote:
> On Wed, Mar 22, 2023 at 02:44:47PM +0200, Kalle Valo wrote:
> > Nathan Chancellor writes:
> >
> > > On Mon, Mar 20, 2023 at 11:26:17AM -0700, Linus Torvalds wrote:
> > >> On Mon, Mar 20, 2023 at 11:05 AM Nathan Chancellor
> >
+ Masahiro and linux-kbuild for the proposal
On Wed, Mar 22, 2023 at 9:56 AM Linus Torvalds
wrote:
>
> On Wed, Mar 22, 2023 at 9:40 AM Sedat Dilek wrote:
> >
> > You have to pass `make LLVM=1` in any case... to `oldconfig` or when
> > adding any MAKEFLAGS like -j${number-of-available-cpus}.
>
>
On Wed, Mar 22, 2023 at 9:40 AM Sedat Dilek wrote:
>
> You have to pass `make LLVM=1` in any case... to `oldconfig` or when
> adding any MAKEFLAGS like -j${number-of-available-cpus}.
I actually think we should look (again) at just making the compiler
choice (and the prefix) be a Kconfig option.
On Wed, Mar 22, 2023 at 1:49 PM Kalle Valo wrote:
>
> Nathan Chancellor writes:
>
> > On Mon, Mar 20, 2023 at 11:26:17AM -0700, Linus Torvalds wrote:
> >> On Mon, Mar 20, 2023 at 11:05 AM Nathan Chancellor
> >> wrote:
> >> >
> >> > On the clang front, I am still seeing the following warning tur
On Wed, Mar 22, 2023 at 02:44:47PM +0200, Kalle Valo wrote:
> Nathan Chancellor writes:
>
> > On Mon, Mar 20, 2023 at 11:26:17AM -0700, Linus Torvalds wrote:
> >> On Mon, Mar 20, 2023 at 11:05 AM Nathan Chancellor
> >> wrote:
> >> >
> >> > On the clang front, I am still seeing the following war
Nathan Chancellor writes:
> On Mon, Mar 20, 2023 at 11:26:17AM -0700, Linus Torvalds wrote:
>> On Mon, Mar 20, 2023 at 11:05 AM Nathan Chancellor wrote:
>> >
>> > On the clang front, I am still seeing the following warning turned error
>> > for arm64 allmodconfig at least:
>> >
>> > drivers/gp
On Mon, Mar 20, 2023 at 3:06 PM Nathan Chancellor wrote:
>
> Right, this seems like a subtle difference in semantics between
> -Wuninitialized between clang and GCC.
I guess it's a bit ambiguous whether it's
"X may be USED uninitialized"
or whether it is
"X may BE uninitialized"
and then de
On Mon, Mar 20, 2023 at 03:06:31PM -0700, Nathan Chancellor wrote:
> It seems like clang takes into account that the branch has no effect on
> how uninitialized err is, although it does acknowledge there may be
> control flow where err is not used uninitialized because it is not used
> at all by st
On Mon, Mar 20, 2023 at 01:30:17PM -0700, Linus Torvalds wrote:
> On Mon, Mar 20, 2023 at 1:05 PM Guenter Roeck wrote:
> >
> > I have noticed that gcc doesn't always warn about uninitialized variables
> > in most architectures.
>
> Yeah, I'm getting the feeling that when the gcc people were tryin
On Mon, Mar 20, 2023 at 1:05 PM Guenter Roeck wrote:
>
> I have noticed that gcc doesn't always warn about uninitialized variables
> in most architectures.
Yeah, I'm getting the feeling that when the gcc people were trying to
make -Wmaybe-uninitialized work better (when moving it into "-Wall"),
t
On Mon, Mar 20, 2023 at 11:26:17AM -0700, Linus Torvalds wrote:
> On Mon, Mar 20, 2023 at 11:05 AM Nathan Chancellor wrote:
> >
> > On the clang front, I am still seeing the following warning turned error
> > for arm64 allmodconfig at least:
> >
> > drivers/gpu/host1x/dev.c:520:6: error: variabl
On Mon, Mar 20, 2023 at 11:53:37AM -0700, Nathan Chancellor wrote:
> On Mon, Mar 20, 2023 at 11:26:17AM -0700, Linus Torvalds wrote:
> > On Mon, Mar 20, 2023 at 11:05 AM Nathan Chancellor
> > wrote:
> > >
> > > On the clang front, I am still seeing the following warning turned error
> > > for arm
On Mon, Mar 20, 2023 at 11:56 AM Nathan Chancellor wrote:
>
> I did see a patch fly by to fix that:
>
> https://lore.kernel.org/20230316082035.567520-3-christian.koe...@amd.com/
>
> It seems like the DRM_TEGRA half of it is broken though:
>
> https://lore.kernel.org/202303170635.a2rsq1wu-...@intel
On Mon, Mar 20, 2023 at 11:49:55AM -0700, Linus Torvalds wrote:
> On Mon, Mar 20, 2023 at 11:26 AM Linus Torvalds
> wrote:
> >
> > Hmm. I do my arm64 allmodconfig builds with gcc, and I'm surprised
> > that gcc doesn't warn about this.
>
> Side note: I'm also wondering why that TEGRA_HOST1X confi
On Mon, Mar 20, 2023 at 11:26:17AM -0700, Linus Torvalds wrote:
> On Mon, Mar 20, 2023 at 11:05 AM Nathan Chancellor wrote:
> >
> > On the clang front, I am still seeing the following warning turned error
> > for arm64 allmodconfig at least:
> >
> > drivers/gpu/host1x/dev.c:520:6: error: variabl
On Mon, Mar 20, 2023 at 11:26 AM Linus Torvalds
wrote:
>
> Hmm. I do my arm64 allmodconfig builds with gcc, and I'm surprised
> that gcc doesn't warn about this.
Side note: I'm also wondering why that TEGRA_HOST1X config has that
ARM dependency in
depends on ARCH_TEGRA || (ARM && COMPILE
On Mon, Mar 20, 2023 at 11:05 AM Nathan Chancellor wrote:
>
> On the clang front, I am still seeing the following warning turned error
> for arm64 allmodconfig at least:
>
> drivers/gpu/host1x/dev.c:520:6: error: variable 'syncpt_irq' is
> uninitialized when used here [-Werror,-Wuninitialized]
On Sun, Mar 19, 2023 at 01:50:21PM -0700, Linus Torvalds wrote:
> So rc3 is fairly big, but that's not hugely usual: it's when a lot of
> the fixes tick up as it takes a while before people find and start
> reporting issues.
...
> Please test and report any issues you find,
On the clang front, I
27 matches
Mail list logo
