Displaying 7 results from an estimated 7 matches for "generalizataion".
Did you mean:
generalisation
2015 May 30
0
[LLVMdev] LLD improvement plan
On May 29, 2015, at 10:08 PM, Rui Ueyama <ruiu at google.com> wrote:
> Large part of the difficulties in development of the current LLD comes from over-generalizataion to share code between pretty much different file formats.
ISTM the problem that's been described isn't that code is shared between file formats, but that an internal representation was chosen based on what MachO required, which in the end turned out to be unsuitable for representing the gr...
2015 May 30
1
[LLVMdev] LLD improvement plan
On Fri, May 29, 2015 at 8:29 PM, James Y Knight <jyknight at google.com> wrote:
>
> On May 29, 2015, at 10:08 PM, Rui Ueyama <ruiu at google.com> wrote:
> > Large part of the difficulties in development of the current LLD comes
> from over-generalizataion to share code between pretty much different file
> formats.
>
> ISTM the problem that's been described isn't that code is shared between
> file formats, but that an internal representation was chosen based on what
> MachO required, which in the end turned out to be unsuitable...
2015 May 30
5
[LLVMdev] LLD improvement plan
...isible chunk. Our current design might need to be
> changed, but starting from scratch only to arrive at the same basic idea
> but now having to effectively maintain two codebases doesn't seem worth it.
>
Large part of the difficulties in development of the current LLD comes from
over-generalizataion to share code between pretty much different file
formats. My observation is that we ended up having to write large amount of
code to share little core even which doesn't really fit well any platform
(an example is the virtual archive file I mentioned above -- that was
invented to hide platform-...
2015 May 30
0
[LLVMdev] LLD improvement plan
...design might need to be
>> changed, but starting from scratch only to arrive at the same basic idea
>> but now having to effectively maintain two codebases doesn't seem worth it.
>>
>
> Large part of the difficulties in development of the current LLD comes
> from over-generalizataion to share code between pretty much different file
> formats. My observation is that we ended up having to write large amount of
> code to share little core even which doesn't really fit well any platform
> (an example is the virtual archive file I mentioned above -- that was
> invent...
2015 May 30
1
[LLVMdev] LLD improvement plan
...>>> changed, but starting from scratch only to arrive at the same basic idea
>>> but now having to effectively maintain two codebases doesn't seem worth it.
>>>
>>
>> Large part of the difficulties in development of the current LLD comes
>> from over-generalizataion to share code between pretty much different file
>> formats. My observation is that we ended up having to write large amount of
>> code to share little core even which doesn't really fit well any platform
>> (an example is the virtual archive file I mentioned above -- that was...
2015 May 30
0
[LLVMdev] LLD improvement plan
On Fri, May 29, 2015 at 1:14 AM, Rui Ueyama <ruiu at google.com> wrote:
> I want to make it clear that I didn't (at least intend to) compromise
> flexibility or beauty of design with short-term performance gain. I was
> trying to do simple things in a simple way for both humans and computers,
> and I believe I did that fairly well. I'd even argue that the new design
2015 May 29
3
[LLVMdev] LLD improvement plan
I want to make it clear that I didn't (at least intend to) compromise
flexibility or beauty of design with short-term performance gain. I was
trying to do simple things in a simple way for both humans and computers,
and I believe I did that fairly well. I'd even argue that the new design
is cleaner and more expressive than before, because the "atom" model is in
some part too