[llvm] r232769 - libLTO, llvm-lto, gold: Introduce flag for controlling optimization level.
Chad Rosier
mcrosier at codeaurora.org
Tue Jul 14 12:03:45 PDT 2015
You're correct, Rafael. You should disregard my suggestion..
Seems this is only a problem for our internal implementation and I was being an overly eager good citizen. :)
Chad
-----Original Message-----
From: Rafael EspĂndola [mailto:rafael.espindola at gmail.com]
Sent: Tuesday, July 14, 2015 2:54 PM
To: mcrosier at codeaurora.org
Cc: Peter Collingbourne; llvm-commits
Subject: Re: [llvm] r232769 - libLTO, llvm-lto, gold: Introduce flag for controlling optimization level.
On 14 July 2015 at 08:15, Chad Rosier <mcrosier at codeaurora.org> wrote:
> Hi Peter,
> Do we need to handle -Os and -Oz better? Currently, these options will
> report a fatal error in the gold plugin.
What should it do?
All that the API has is a "unsigned optLevel". It is not clear if we should have a size optimization option at this point. All cases that need size optimization should already be converted to function attributes, no?
Cheers,
Rafael
More information about the llvm-commits
mailing list