Re: Thoughts about introducing OPTIMIZATION_CFLAG

2016-01-04 Thread Michal Marek
Dne 4.1.2016 v 12:47 Sedat Dilek napsal(a): > But I think you did not get my problem - to have two different > optimization-levels for a compiler in *one* make-line makes no sense > to me. That we sometimes have -O2 ... -Os on the command line is not a problem, since any same unix tool parses its

Re: Thoughts about introducing OPTIMIZATION_CFLAG

2016-01-04 Thread Sedat Dilek
On Mon, Jan 4, 2016 at 12:33 PM, One Thousand Gnomes wrote: >> As said... I checked only for x86 and acpi only. >> >> For example '-Os' is hardcoded in... >> >> arch/x86/Makefile >> arch/x86/purgatory/Makefile >> >> drivers/acpi/Makefile >> drivers/acpi/acpica/Makefile >> >> For acpi part we have

Re: Thoughts about introducing OPTIMIZATION_CFLAG

2016-01-04 Thread One Thousand Gnomes
> As said... I checked only for x86 and acpi only. > > For example '-Os' is hardcoded in... > > arch/x86/Makefile > arch/x86/purgatory/Makefile > > drivers/acpi/Makefile > drivers/acpi/acpica/Makefile > > For acpi part we have currently both used '-O2' and '-Os' ('-Oz' for > llvmlinux) in appro

Re: Thoughts about introducing OPTIMIZATION_CFLAG

2016-01-04 Thread Sedat Dilek
On Mon, Jan 4, 2016 at 11:54 AM, Sedat Dilek wrote: > [ Not sure if I have addressed all the correct people and mailing-lists ] > > Hi, > > while still digging into a llvmlinux issue with workqueue I saw that > the wrong optimization compiler-flag was used on x86 architecture and > acpi subsystem.

Thoughts about introducing OPTIMIZATION_CFLAG

2016-01-04 Thread Sedat Dilek
[ Not sure if I have addressed all the correct people and mailing-lists ] Hi, while still digging into a llvmlinux issue with workqueue I saw that the wrong optimization compiler-flag was used on x86 architecture and acpi subsystem. CLANG requires '-Oz' whereas GCC requires '-Os'. As acpi-daemo