Hi,
On 26 October 2017 at 14:13, R0b0t1 wrote:
> On Thu, Oct 19, 2017 at 8:46 AM, Geoff Wozniak wrote:
>> R0b0t1 writes:
>>>
>>> When I first looked at the GCC codebase, it seemed to me that most
>>> operations should be done on the GIMPLE representation as it contains the
>>> most information.
On Thu, Oct 19, 2017 at 8:46 AM, Geoff Wozniak wrote:
> R0b0t1 writes:
>>
>> When I first looked at the GCC codebase, it seemed to me that most
>> operations should be done on the GIMPLE representation as it contains the
>> most information. Is there any reason you gravitated towards RTL?
>
>
> N
R0b0t1 writes:
When I first looked at the GCC codebase, it seemed to me that
most operations should be done on the GIMPLE representation as
it contains the most information. Is there any reason you
gravitated towards RTL?
Naiveté, really.
My team and I didn’t know much about the code base
Hello,
On Fri, Oct 13, 2017 at 1:18 PM, Geoff Wozniak wrote:
> The code structure suggests that we should
> either do an IPA pass on GIMPLE or we work as an assembler pass, thus
> forgoing work on RTL at all. Is this is what we should be doing?
When I first looked at the GCC codebase, it seemed
On 10/13/2017 12:18 PM, Geoff Wozniak wrote:
> My team and I are working on a procedural abstraction (PA) optimization
> for GCC based on the ARM Embedded Toolchain distribution that uses GCC
> 6.2.1. Our initial attempt to get something functional has been
> successful, but it is a very messy solu
My team and I are working on a procedural abstraction (PA)
optimization for GCC based on the ARM Embedded Toolchain
distribution that uses GCC 6.2.1. Our initial attempt to get
something functional has been successful, but it is a very messy
solution because we don't see a reasonable way to do
