search for: attributes

Displaying 20 results from an estimated 14136 matches for "attributes".

Did you mean: attribute
2012 Nov 20
0
[LLVMdev] [RFC] Passing Options to Different Parts of the Compiler Using Attributes
On Nov 13, 2012, at 12:20 AM, Bill Wendling wrote: > IR Changes > ---------- > > The attributes will be specified within the IR. This allows us to generate code > that the user wants. This also has the advantage that it will no longer be > necessary to specify all of the command line options when compiling the bit code > (via 'llc' or 'clang'). E.g., '-mcpu=cortex...
2012 Nov 13
9
[LLVMdev] [RFC] Passing Options to Different Parts of the Compiler Using Attributes
Hi! This is a proposal to expand the Attributes class to support many different options that will be accessible by all parts of the compiler. Please read and give any feedback you may have. Thanks! -bw Passing Options to Different Parts of the Compiler Problem ======= There is a growing need to pass information from the front-en...
2013 Jan 29
4
[LLVMdev] [RFC] Attributes Rewrite (Final)
Hi! The rewrite of the attributes class is well underway. The next step is to add support for the expanded rĂ´le of attributes in the language and IR. This is the final proposal for the language changes. There isn't a lot of new information except for the syntax changes for the new feature. Executive Summary: The new syntax is...
2012 Nov 26
3
[LLVMdev] [RFC] Passing Options to Different Parts of the Compiler Using Attributes
On Nov 20, 2012, at 11:03 AM, Meador Inge <meadori at codesourcery.com> wrote: > On Nov 13, 2012, at 12:20 AM, Bill Wendling wrote: > >> IR Changes >> ---------- >> >> The attributes will be specified within the IR. This allows us to generate code >> that the user wants. This also has the advantage that it will no longer be >> necessary to specify all of the command line options when compiling the bit code >> (via 'llc' or 'clang'). E.g., '...
2012 Nov 21
1
[LLVMdev] [RFC] Passing Options to Different Parts of the Compiler Using Attributes
On Tue, Nov 20, 2012 at 11:03 AM, Meador Inge <meadori at codesourcery.com> wrote: > > On Nov 13, 2012, at 12:20 AM, Bill Wendling wrote: > >> IR Changes >> ---------- >> >> The attributes will be specified within the IR. This allows us to generate code >> that the user wants. This also has the advantage that it will no longer be >> necessary to specify all of the command line options when compiling the bit code >> (via 'llc' or 'clang'). E.g., '...
2013 Feb 09
3
[LLVMdev] Using the New Attributes Classes
Using the New Attributes Classes Attributes in LLVM have changed in some fundamental ways. It was necessary to do this to support expanding the attributes to encompass more than a handful of attributes --- e.g. command line options. The old way of handling attributes consisted of representing them as a bit mask of values....
2018 Oct 04
0
[PATCH v2 2/4] common/utils: Move libxml2 writer macros to a common header file.
...t: + * + * empty_element ("name"); + * + * which produces C<<< <name/> >>> + */ +#define empty_element(element) \ + do { start_element ((element)) {} end_element (); } while (0) + +/** + * To define an XML element with attributes, use: + * + * start_element ("name") { + * attribute ("foo", "bar"); + * attribute ("count", "%d", count); + * ... + * } end_element (); + * + * which produces C<<< <name foo="bar" count="123">...<...
2013 Feb 03
0
[LLVMdev] [RFC] Attributes Rewrite (Final)
On Jan 29, 2013, at 2:42 PM, Bill Wendling <isanbard at gmail.com> wrote: > Executive Summary: > > The new syntax is: > > #0 = attributes { noinline align=4 "cpu"="cortex-a8" } > #1 = attributes { attr = (val1 val2 val3) } > #bork = attributes { sspreq noredzone } > > define void @foo() #0 #bork { ret void } The general syntax LGTM. It seems clean and fits well with what we have. > The 'a...
2007 Jun 19
3
Nil object for nested resource
Hi all, I have 2 models with a standard 1 to many relationship. I''m also using REST on the two models and have added the appropriate code to the routes.rb file. scorecard.rb: class Scorecard < ActiveRecord::Base has_many :attributes end attribute.rb: class Attribute < ActiveRecord::Base belongs_to :scorecard end routes.rb: map.resources :scorecards do |scorecard| scorecard.resources :attributes end My problem is that I want to show a single scorecard with all it''s attributes. I then want to display a "...
2010 Mar 13
2
Error with winemp3.acm for Sony ereader software
I am trying to run the ereader bookstore software from Sony/Borders. It installed without any errors, but I get this error when I try to run the program: err:module:load_builtin_dll failed to load .so lib for builtin L"winemp3.acm": libmpg123.so.0: cannot open shared object file: No such file or directory Google did not return any useful results. I am running Debian squeeze:
2015 Feb 12
3
[LLVMdev] [RFC] Storing default function attributes on the module
...et explicitly, but the plan of record is for `clang` to explicitly encode all (or most) CodeGen options -- even the target defaults. Changing `clang` to store target defaults on the module will allow us to continue to override them when running `llc`. The right precedence would be: 1. Explicit attributes set on the function. 2. `llc` command-line options. 3. Default function attributes stored on the module. (Outside of `llc`, skip step 2.) In `lib/Linker` (i.e., `llvm-lto`, `llvm-link`, `libLTO.dylib`), defaults should be pushed down as explicit function attributes. Default function-leve...
2015 Feb 24
2
[LLVMdev] [RFC] Storing default function attributes on the module
...in your mail though so please feel free to > explain at me :) > > > > > > Changing `clang` to store target defaults on the module will allow us to > > continue to override them when running `llc`. The right precedence > > would be: > > > > 1. Explicit attributes set on the function. > > 2. `llc` command-line options. > > 3. Default function attributes stored on the module. > > > > (Outside of `llc`, skip step 2.) > > > > In `lib/Linker` (i.e., `llvm-lto`, `llvm-link`, `libLTO.dylib`), > > defaults should be...
2015 Feb 24
2
[LLVMdev] [RFC] Storing default function attributes on the module
...questions. I may have misunderstood some things in your mail though so please feel free to explain at me :) > Changing `clang` to store target defaults on the module will allow us to > continue to override them when running `llc`. The right precedence > would be: > > 1. Explicit attributes set on the function. > 2. `llc` command-line options. > 3. Default function attributes stored on the module. > > (Outside of `llc`, skip step 2.) > > In `lib/Linker` (i.e., `llvm-lto`, `llvm-link`, `libLTO.dylib`), > defaults should be pushed down as explicit function a...
2012 Sep 19
8
[LLVMdev] [RFC] Overhauling Attributes
Overhauling Attributes Problem ======= LTO needs a way to pass options through to different parts of the compiler. In particular, we need to pass code generation options to the back-end. The way we want to do this is via the LLVM Attributes class. In order to do that, we need to overhaul the Attributes class. The Attr...
2007 May 30
9
Specify attr_protected
This is kind of a two part question. Question One: I want to be sure that an Order model is protecting sensitive attributes from mass assignment. The example looks like this: describe Order do it "should protect total attribute from mass assignment" do @order = Order.new(:total => 0.05) @order.total.should_not == 0.05 end end And the code to implement it: class Order < ActiveRecord::Base...
2006 Jun 13
7
ActiveRecord attribute= overload
I want to overload the = operator for one of the attributes in a model to run a filter on the input. However I can''t do this: def attribute=(data) self.attribute = filter(data) end because that creates an infinite recursive loop. How do I get around this? -- Posted via http://www.ruby-forum.com/.
2019 Mar 14
4
[RFC] We are running out of slots in the Attribute::AttrKind enum
I would like to add a target-dependent attribute to the LLVM IR, and the guidance in http://llvm.org/docs/HowToUseAttributes.html says that target-dependent attributes should not occupy a slot in the Attribute::AttrKind enum, but I have yet to find an attribute that is represented in the IR that does not also have a slot in the AttrKind enum. We are limited to 63 slots in the AttrKind enum because it is represented in t...
2015 Feb 26
1
[LLVMdev] [RFC] Storing default function attributes on the module
...el free to >> explain at me :) >> > >> > >> > Changing `clang` to store target defaults on the module will allow us to >> > continue to override them when running `llc`. The right precedence >> > would be: >> > >> > 1. Explicit attributes set on the function. >> > 2. `llc` command-line options. >> > 3. Default function attributes stored on the module. >> > >> > (Outside of `llc`, skip step 2.) >> > >> > In `lib/Linker` (i.e., `llvm-lto`, `llvm-link`, `libLTO.dylib`), >...
2019 Apr 30
3
RFC - a proposal to support additional symbol metadata in ELF object files in the ARM compiler
Hello All, In ARM embedded applications, there are some compilers that support useful function and variable attributes that help the compiler communicate information about symbols to downstream object consumers (i.e. linkers). One such attribute is the "location" attribute. This attribute can be applied to a global or local static data object or a function to indicate to the linker that the definition of...
2012 Nov 13
0
[LLVMdev] [RFC] Passing Options to Different Parts of the Compiler Using Attributes
Couple of quick questions: First, what are the valid types for <value>? Are they always strings which the target must interpret, or will numeric literals and booleans also be supported? Also, in the proposal, attributes are sometimes quoted and sometimes they are not. I know this is nit-picking, but what is the preferred syntax? Second, would it make sense to fold the calling convention into this set of attributes? For correctness, attributes cannot be stripped from the IR anyway (as I understand it). The exis...