Re: Compiling Linux with "bdver2" gcc optimization option

2019-08-21 Thread Étienne Mollier
Franco Martelli, on 2019-08-20: > mm/memory.o: warning: objtool: remap_pfn_range()+0xd5: unsupported > intra-function call > > that it's part of linux-kbuild-4.19 package maybe I should submit a bug > report to this package or is another one a better choice? Hi Franco, Should you submit a bug

Re: Compiling Linux with "bdver2" gcc optimization option

2019-08-20 Thread Franco Martelli
On 19/08/19 at 21:18, Étienne Mollier wrote: > Franco Martelli, on 2019-08-19: >> I was thinking to submit a bug report against gcc-8 package. Now that I >> have a work around, "bdver1" compiles without warnings, I can say >> enough, what do you think about? > > I don't know, to me it sounds more

Re: Compiling Linux with "bdver2" gcc optimization option

2019-08-19 Thread Étienne Mollier
Franco Martelli, on 2019-08-19: > I was thinking to submit a bug report against gcc-8 package. Now that I > have a work around, "bdver1" compiles without warnings, I can say > enough, what do you think about? I don't know, to me it sounds more like little bugs on kernel side, patches silencing

Re: Compiling Linux with "bdver2" gcc optimization option

2019-08-19 Thread Franco Martelli
I was thinking to submit a bug report against gcc-8 package. Now that I have a work around, "bdver1" compiles without warnings, I can say enough, what do you think about? Best regards -- Franco Martelli

Re: Compiling Linux with "bdver2" gcc optimization option

2019-08-16 Thread Étienne Mollier
Franco Martelli, on 2019-08-16: > On 16/08/19 at 17:22, Étienne Mollier wrote: [...] > > Compilers may have good optimization routines to boost the speed > > of the code in several situations, but in other ones there are > > trade-offs to take between size and performance of the code. I > >

Re: Compiling Linux with "bdver2" gcc optimization option

2019-08-16 Thread Franco Martelli
On 16/08/19 at 17:22, Étienne Mollier wrote: > Bonjour, > > Woops, this sounds a bit like I might not have used a very clear > wording. If I were at your place, I would proceed so; but I > don't have a Piledriver CPU to do actual testing on my side. > I'm still stuck with an old K10, not to

Re: Compiling Linux with "bdver2" gcc optimization option

2019-08-16 Thread Étienne Mollier
Bonjour, Franco Martelli, on 2019-09-14: > On 13/08/19 at 19:35, Étienne Mollier wrote: [...] > > I would do a few tests with a virtual > > machine supporting bdver2 instructions before going live anyway, > > and backups stored far away from the machine once testing, and > >

Re: Compiling Linux with "bdver2" gcc optimization option

2019-08-14 Thread Franco Martelli
On 13/08/19 at 19:35, Étienne Mollier wrote: > Hi Franco, > > I'm not fluent enough in GCC 8 for x86_64 to answer to all the > various warnings you indicated. Some may be harmless, and some > may eat your data. I would do a few tests with a virtual > machine supporting bdver2 instructions

Re: Compiling Linux with "bdver2" gcc optimization option

2019-08-13 Thread Étienne Mollier
Franco Martelli , on 2019-09-13: > Hi, everybody > > in order to achieve Linux kernel optimized for my CPU AMD FX-8350 > Bulldozer2 I changed the line 121 of linux-source-4.19/arch/x86/Makefile > from: > > cflags-$(CONFIG_MK8) += $(call cc-option,-march=k8) > > to: > > cflags-$(CONFIG_MK8) +=

Compiling Linux with "bdver2" gcc optimization option

2019-08-13 Thread Franco Martelli
Hi, everybody in order to achieve Linux kernel optimized for my CPU AMD FX-8350 Bulldozer2 I changed the line 121 of linux-source-4.19/arch/x86/Makefile from: cflags-$(CONFIG_MK8) += $(call cc-option,-march=k8) to: cflags-$(CONFIG_MK8) += $(call cc-option,-march=bdver2) \