Displaying 5 results from an estimated 5 matches for "messyness".
Did you mean:
messiness
2006 Feb 07
4
Ruby, Rails & Inheritance
Hi!
I am looking for a solution for the following problem:
Some of my models share some attributes and also was in need for some
extra features, so I created a class "RecordWithFeatures":
-----------------------------------------------------------------
class RecordWithFeatures < ActiveRecord::Base
# @Override
def self.descends_from_active_record?
superclass ==
2010 Nov 16
1
[LLVMdev] Build Attributes Proposal
...t know how common it is for the same executable to
cross thumb boundaries - (given that16bit thumb has limits on register
usage etc..) but I suppose its possible.
For now, I agree with Renato that using the Module-Level Inline
Assembly is probably not the right way to go - for example, some of
the messyness of .cpu asm statement mapping to many FileScope
attributes is the primary cause of the (likely) not-clean looking code
that needs to go into the current .ARM.attributes emitter for ELF.
What I would like to find out is the current set of supported ASM
attributes by the current AEABI compiler. Once...
2010 Nov 13
0
[LLVMdev] Build Attributes Proposal
On 13 November 2010 21:15, Duncan Sands <baldrick at free.fr> wrote:
> Since I don't know anything about these attributes, talk of indexes and
> so forth goes straight over my head.
Hi Duncan,
I assumed you knew what build attributes were in the first place, my mistake.
For a full explanation of what they are, see ARM ABI Addenda, section
2.1 (PDF). (Google's first hit for
2010 Nov 13
2
[LLVMdev] Build Attributes Proposal
Hi Renato,
> On 13 November 2010 15:12, Duncan Sands<baldrick at free.fr> wrote:
>> I agree that it's limited. As for MC, it will need to handle these strings
>> anyway since this is an existing LLVM feature (coming from gcc originally)
>> that needs to be supported.
>
> Do you mean that LLVM-GCC generates build attributes as asm strings in IR?
no, I mean
2008 Dec 31
5
The future of Compiz
Where are we going?
It's time to start thinking ahead and really figure out how to make Compiz
survive, specially in lieu of Dennis' suggestion.
The reality is that there has been the equivalent of no progress since the
merge. We've basically only been in maintenance mode. The reason for this,
from my point of view, is a complete lack of direction and leadership.
We've