Snapshot gcc-5-20160628 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/5-20160628/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 5 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-5
Hi,
For handling PHI, it expects cfg to be built before. So I was
wondering how are we going to handle this? Do we need to build cfg
while parsing only?
Thanks,
Prasad
On Fri, Jun 17, 2016 at 5:31 PM, Kyrill Tkachov
wrote:
> Hi all,
>
> I'm working on a tree-ssa pass to implement PR 22141, a pass that merges
> adjacent stores.
> I've gotten to the point where I can identify the adjacent accesses, merge
> them into a single value
> and am now working on emitting
> Ok, thanks for your reply. The 4.6 backend was testing if the hardware
> FP was live, and did some optimization whatever -fomit-frame-pointer or
> -fno-omit-frame-pointer. So it was not a valid optimization?
It was sort of a bug since -fno-omit-frame-pointer is in effect unless you
specify othe
>> I'm porting a private backend from an old 4.6 branch to the 6.1.0
>> release, and I have some troubles eliminating my frame pointer without
>> -fomit-frame-pointer option.
>> Elimination is correctly done with -fomit-frame-pointer.
> If the target's default is -fno-omit-frame-pointer, then it's
