search for: sections

...he simple queries that load the attributes of an ActiveRecord object. In the transcript below, the record with id 0 gets fetched *eight times* during one request! This will become a terrible performance problem -- scaling as O(n^2) -- as the database grows. The table in question, ''sections'', uses acts_as_tree. In rendering each section, the app walks up the tree to find the path to the root, using the accessor Section#parent. I''m guessing that what''s happening is that Section#parent always allocates a new Section object (and fetches its contents fro...

This idea popped up in the review thread for https://reviews.llvm.org/D25627 . Problem: Currently, LLD creates special sections that are not just concatenations of input sections but need link-time data generation, such as .got, .plt, interp, .mips.options, etc., as output sections. We have OutputSectionBase subclasses (e.g. GotSection, PltSection, etc.) to create data. Even though this scheme works in most cases, there are...

...afeness" is not an attribute of the section but of the symbol, I > think. The symbol is "safe" if there's no direct reference to the symbol > data. All references should go through relocations. A section may contain > both "safe" and "unsafe" symbols. Sections contain symbols. In the context of ELF, marking sections as safe/not is more desirable because of the switches (-ffunction-sections and -fdata-sections available already). > - How about making the compiler to create a new section for each "safe" > atom, as it does for inline fu...

I would suggest converting only part of linker generated sections to input sections to reduce amount of code changes. For example it's unlikely that SymbolTableSection or StringTableSection would ever require such treatment, so why converting them to input sections? 2016-10-19 11:03 GMT+03:00 George Rimar <grimar at accesssoftek.com>: >>This ide...

Is there any reason -ffunction-sections and -fdata-sections wouldn't work? If it'll work, it may be be better to say "if you want to get a better linker output use these options", rather than defining new ELF section. On Thu, Jul 25, 2013 at 2:01 PM, Shankar Easwaran <shankare at codeaurora.org>wrote: > On 7...

On Wed, Oct 19, 2016 at 3:34 AM, Peter Smith via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Thanks for the RFC. > > I'm in favour of the option of creating InputSections for some linker > generated content. I think it would add extra flexibility to the > linker. ARM's proprietary linker uses the equivalent of InputSections > with a pseudo linker defined ObjectFile for SHF_ALLOC content. As > Eugene points out it isn't always appropriate for meta...

Hi, We’d like to propose an extension to both the map file and the print-gc/icf-sections output. This extension would be to report the pieces of .eh_frame and SHF_MERGE sections in these files somehow. Since all (or at least the majority) of the contents of these sections in the output come from inputs, it would be beneficial in trying to associate the output contents with where they c...

I am a little stuck with getting an sql result into my page. I want to run a select distinct that returns all of the different sections available and displays this as a form select. In my controller I have: def edit @resource = Resource.find(params[:id]) @sections = Resource.find_by_sql "SELECT DISTINCT resources.section FROM resources" end And then in my view I have: <% for option in @sections %> &lt...

Not all users compile their code with -ffunction-sections and -fdata-sections. This is to handle usecases when libraries use a mix of object files too. On 7/25/2013 4:10 PM, Rui Ueyama wrote: > Is there any reason -ffunction-sections and -fdata-sections wouldn't work? > If it'll work, it may be be better to say "if you want to get a...

...ly lld ties up all atoms in a section for ELF together. This proposal just breaks it by handling it differently. *This requires **NO ELF ABI changes. *_*Definitions :-*_ A section is not considered safe if there is some code that appears to be present between function boundaries (or) optimizes sections to place data at the end or beginning of a section (that contains no symbol). A section is considered safe if symbols contained within the section have been associated with their appropriate sizes and there is no data present between function boundaries. Examples of safe sections are, code gen...

Hi all, I'd like to propose that LLVM IR have a mechanism to describe sections in a more explicit way than we can today. Currently, we provide an attribute called "section" on GlobalVariables and Functions. This attribute will choose which section the Value will end up in. However, it does not describe the attributes of the section. Without a way of describing the...

...tion for ELF together. This > proposal just breaks it by handling it differently. > > *This requires **NO ELF ABI changes. > > **Definitions :-* > > A section is not considered safe if there is some code that appears to be > present between function boundaries (or) optimizes sections to place data > at the end or beginning of a section (that contains no symbol). > > A section is considered safe if symbols contained within the section have > been associated with their appropriate sizes and there is no data present > between function boundaries. > > Examples...

...ng built with -fno- exceptions: http://llvm.org/PR2481. Just the excess labels alone give the assembler a lot more work to do. 2. The __debug_info section is twice as big and the __debug_line section is a bit bigger: http://llvm.org/PR2482 3. We aren't outputting text or data __const_coal sections. I'm not sure what these are, but they seem preferable to __textcoal_nt: http://llvm.org/PR2483 Also, we have no __debug_pubtypes, __debug_aranges, __debug_str, __debug_ranges or sections. I have no idea what these are, but could be a problem :) Fixing these are important for a couple...

Hi llvm-dev, I'm currently looking for alternatives to the synthetic references that XRay uses to keep some side-tables live, to avoid linker garbage collection from deleting those sections. Before going any further, let me give a backgrounder on what XRay does today. Background ========== XRay has two side tables we use at runtime to identify the location of the sleds for the functions that are instrumented. These are named "xray_fn_idx" and "xray_instr_map". We...

On Jul 29, 2013, at 10:09 AM, Shankar Easwaran wrote: > On 7/29/2013 11:24 AM, Nick Kledzik wrote: >> On Jul 25, 2013, at 2:10 PM, Rui Ueyama wrote: >>> Is there any reason -ffunction-sections and -fdata-sections wouldn't work? If it'll work, it may be be better to say "if you want to get a better linker output use these options", rather than defining new ELF section. >> >From my understanding, -ffunction-sections is a good semantic match. But it introduces a...

...30: Dropping empty section \references prepare_Rd: sqLiteConnect.Rd:40-42: Dropping empty section \seealso * checking Rd metadata ... OK * checking Rd cross-references ... OK * checking for missing documentation entries ... OK * checking for code/documentation mismatches ... OK * checking Rd \usage sections ... OK * checking Rd contents ... OK * checking for unstated dependencies in examples ... OK * checking data for non-ASCII characters ... OK * checking examples ... OK * checking PDF version of manual ... OK > sessionInfo() R version 2.12.2 (2011-02-25) Platform: i686-pc-linux-gnu (32-bit)...

On Mon, 2017-03-06 at 08:37 +1100, Tom Robinson via samba wrote: > Full back trace provided in previous message. Still don't know why > samba-tool is crashing. Any help > is appreciated. Can you run testparm over the smb.conf file? I think it may be refusing to load it. Andrew Bartlett

I use eMule 0.50a with wine 1.1.43, and crashes every day. I am attaching the log. Code: Xlib: extension "Generic Event Extension" missing on display ":1.0". Xlib: extension "Generic Event Extension" missing on display ":1.0". fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC90.CRT" (9.0.21022.8) Xlib:

Hi, Many linkers including lld have a feature to eliminate unused sections from output to make output smaller (which is essentially a mark-sweep gc where sections are vertices and relocations are edges). lld and GNU gold have yet another feature, ICF, to merge functions by contents to save more space. When we remove or merge a function, we want to eliminate its exception...

No I haven't. Thank you for the pointer. Looks like the problem of the inverted edges was discussed there. But I guess my bigger question is this: why do we still create one big .eh_frame even if -ffunction-sections is given? When the option is given, Clang creates .text, .rela.text and .gcc_exception_table sections for each function, but it still creates a monolithic .eh_frame that covers all function sections, which seems odd to me. On Thu, Oct 26, 2017 at 9:47 AM, Reid Kleckner <rnk at google.com> w...