search for: cus

Le lundi 30 mars 2020 ? 15:24 +1300, Paul Murrell a ?crit : > Hi > > I have created an R branch that contains a potential fix ... > > https://svn.r-project.org/R/branches/R-symfam/ > > This allows, for example, ... > > cairo_pdf(symbolfamily="OpenSymbol") > > ... to specify that the OpenSymbol family should be used as the > "symbol" font

...native dll. the win.ini file does exist, it is 0 bytes. any ideas? thanks john baxter rh linux 7.1 wine 20010426-1 here is some of the output, just prior to the messagebox. the last file activity is on win.ini trace:dosfs:DOSFS_DoGetFullPathName got C:\Program Files\TC2000\User\Data\WordenIG.cus trace:dosfs:DOSFS_DoGetFullPathName returning 'C:\Program Files\TC2000\User\Data\WordenIG.cus' trace:dosfs:DOSFS_GetFullName C:\Program Files\TC2000\User\Data\WordenIG.cus (last=0) trace:dosfs:DOSFS_FindUnixName /usr/share/wine-c,Program Files\TC2000\User\Data\WordenIG.cus trace:dosfs:DOSFS...

...gt; > need Symbol, or OpenSymbol, or any special font setup. > > Agreed. I got reasonable coverage from DejaVu Sans and FreeSerif. > There are still a number of ASM code points that are not covered > though, > for example, ... > > F8EB E6 # LEFT PAREN TOP # parenlefttp (CUS) > F8EC E7 # LEFT PAREN EXTENDER # parenleftex (CUS) > F8ED E8 # LEFT PAREN BOTTOM # parenleftbt (CUS) > > Even OpenSymbol is missing a few (though perhaps not very common > ones) ... All the F8* codepoints are in the private use area. That means you can?t rely on them existing in...

...nospace fontconfig defaults. You don?t > need Symbol, or OpenSymbol, or any special font setup. Agreed. I got reasonable coverage from DejaVu Sans and FreeSerif. There are still a number of ASM code points that are not covered though, for example, ... F8EB E6 # LEFT PAREN TOP # parenlefttp (CUS) F8EC E7 # LEFT PAREN EXTENDER # parenleftex (CUS) F8ED E8 # LEFT PAREN BOTTOM # parenleftbt (CUS) Even OpenSymbol is missing a few (though perhaps not very common ones) ... F8E5 60 # RADICAL EXTENDER # radicalex (CUS) F8E6 BD # VERTICAL ARROW EXTENDER # arrowvertex (CUS) F8E7 BE # HORIZONTAL ARR...

...the intention of the DWARF specification (though not explicitly forbidden), since there is an implied 1-1 relationship between skeleton CU and .dwo. There is an explicit 1-1 relationship between skeleton CU and split-full CU (not .dwo). This suggests to me that if you want a .dwo to have multiple CUs, then the .o should have multiple corresponding skeleton CUs. Each skeleton/split-full pair would have the same dwo_name but different dwo_IDs. You're making it sound like LTO is actually producing only one skeleton CU? That would be a bug. I am not finding anywhere that explicitly says a ....

...> > >> > So Dehao and I have been dealing with some of the nitty gritty details of debug info with ThinLTO, specifically with Fission(Split DWARF). >> > >> > This applies to LTO as well, so I won't single out ThinLTO here. >> > >> > 1) Multiple CUs in a .dwo file >> > Clang/LLVM produces a CU for each original source file - these CUs are kept through IR linking (thin or full) and produced as distinct CUs in the resulting DWARF. >> > This preserves semantics as much as possible - eg: file-local functions and types (those in a...

...com> wrote: > > > > So Dehao and I have been dealing with some of the nitty gritty details > of debug info with ThinLTO, specifically with Fission(Split DWARF). > > > > This applies to LTO as well, so I won't single out ThinLTO here. > > > > 1) Multiple CUs in a .dwo file > > Clang/LLVM produces a CU for each original source file - these CUs are > kept through IR linking (thin or full) and produced as distinct CUs in the > resulting DWARF. > > This preserves semantics as much as possible - eg: file-local functions > and types (tho...

...OpenSymbol, or any special font setup. >> >> Agreed. I got reasonable coverage from DejaVu Sans and FreeSerif. >> There are still a number of ASM code points that are not covered >> though, >> for example, ... >> >> F8EB E6 # LEFT PAREN TOP # parenlefttp (CUS) >> F8EC E7 # LEFT PAREN EXTENDER # parenleftex (CUS) >> F8ED E8 # LEFT PAREN BOTTOM # parenleftbt (CUS) >> >> Even OpenSymbol is missing a few (though perhaps not very common >> ones) ... > > All the F8* codepoints are in the private use area. That means you &g...

So Dehao and I have been dealing with some of the nitty gritty details of debug info with ThinLTO, specifically with Fission(Split DWARF). This applies to LTO as well, so I won't single out ThinLTO here. 1) Multiple CUs in a .dwo file Clang/LLVM produces a CU for each original source file - these CUs are kept through IR linking (thin or full) and produced as distinct CUs in the resulting DWARF. This preserves semantics as much as possible - eg: file-local functions and types (those in anonymous namespaces or decla...

So I've been looking at a particular performance problem with LLVM's symbolizer due to the use of ThinLTO, split DWARF, and split DWARF inlining info. This combination has a couple of problems: 1) it means multiple CUs in a single DWO, which isn't well defined/specified, and best avoided - so I'm working on fixing that here (won't fix split DWARF+Full LTO) because we already don't use cross-CU references in the split units (because there's no supported way to express that in DWARF), so we clon...

...sonable to me and maps well to the CU masking > > > >>>> feature in our GPUs. > > > >>>> > > > >>>> It would also allow us to do more coarse-grained masking for example to > > > >>>> guarantee balanced allocation of CUs across shader engines or > > > >>>> partitioning of memory bandwidth or CP pipes (if that is supported by > > > >>>> the hardware/firmware). > > > >>> Hm, so this sounds like the definition for how this cgroup is supposed to > > >...

...wrote: > > > > So I've been looking at a particular performance problem with LLVM's > symbolizer due to the use of ThinLTO, split DWARF, and split DWARF inlining > info. > > > > This combination has a couple of problems: > > > > 1) it means multiple CUs in a single DWO, which isn't well > defined/specified, and best avoided - so I'm working on fixing that here > (won't fix split DWARF+Full LTO) because we already don't use cross-CU > references in the split units (because there's no supported way to express > that i...

...ct 16, 2013 at 10:54 AM, Manman Ren <manman.ren at gmail.com>wrote: >> >>> >>> >>> >>> On Tue, Oct 15, 2013 at 5:59 PM, David Blaikie <dblaikie at gmail.com>wrote: >>> >>>> >>>> In beginModule, we construct the CUs, but not all the DIEs that >>>>>>> belong to the CU. >>>>>>> In endFunction, we started to construct the scope DIEs. So in some >>>>>>> sense, we are adding things to prior CUs. >>>>>>> >>>>>>>...

...Ren <manman.ren at gmail.com>wrote: >>> >>>> >>>> >>>> >>>> On Tue, Oct 15, 2013 at 5:59 PM, David Blaikie <dblaikie at gmail.com>wrote: >>>> >>>>> >>>>> In beginModule, we construct the CUs, but not all the DIEs that >>>>>>>> belong to the CU. >>>>>>>> In endFunction, we started to construct the scope DIEs. So in some >>>>>>>> sense, we are adding things to prior CUs. >>>>>>>> >>>&...

...In the input IR there is a strangely formed (but correct) debug info MD that causes duplication of existing DICompileUnit during cloning, but llvm.dbg.cu is not updated. I got around by a quick cleanup pass that detects the situation and simply adds them in… Something like this: > > auto *CUs = F->getParent()->getNamedMetadata("llvm.dbg.cu"); > if (!CUs) > return; > > SmallPtrSet<Metadata *, 2> Listed; > Listed.insert(CUs->op_begin(), CUs->op_end()); > > for (auto *CU : CUVisited) > if (!Listed.count(CU)) { >...

...oughts: >>>>>>>>>>>> >>>>>>>>>>>> 0001: >>>>>>>>>>>> This patch generally, while separated for legibility, is >>>>>>>>>>>> untested & difficult to discuss in isolation. >>>>>>>>>>>> >>>>>>>>>>> I agree, this patch adds the functionality but does not use it, >>>>>>>>>>> the 2nd patch uses ref_addr. >>>>>>>>>>> If you...

Yeah, fair - I'll give it a week or something, see if Paul or anyone else has ideas about why the existing behavior might be useful before I remove it. On Wed, Nov 28, 2018 at 10:27 AM Adrian Prantl <aprantl at apple.com> wrote: > > On Nov 28, 2018, at 9:50 AM, David Blaikie <dblaikie at gmail.com> wrote: > > > > a) decide that a unit without ranges covers no

> In beginModule, we construct the CUs, but not all the DIEs that belong to >>> the CU. >>> In endFunction, we started to construct the scope DIEs. So in some >>> sense, we are adding things to prior CUs. >>> >>> Looking at void CompileUnit::addDIEEntry(DIE *Die, uint16_t Attribute, >>&...

On Wed, Oct 16, 2013 at 10:54 AM, Manman Ren <manman.ren at gmail.com> wrote: > > > > On Tue, Oct 15, 2013 at 5:59 PM, David Blaikie <dblaikie at gmail.com> wrote: > >> >> In beginModule, we construct the CUs, but not all the DIEs that belong >>>>> to the CU. >>>>> In endFunction, we started to construct the scope DIEs. So in some >>>>> sense, we are adding things to prior CUs. >>>>> >>>>> Looking at void CompileUnit::addDIEEntry...

...;>>> thoughts: >>>>>>>>>>> >>>>>>>>>>> 0001: >>>>>>>>>>> This patch generally, while separated for legibility, is >>>>>>>>>>> untested & difficult to discuss in isolation. >>>>>>>>>>> >>>>>>>>>> I agree, this patch adds the functionality but does not use it, >>>>>>>>>> the 2nd patch uses ref_addr. >>>>>>>>>> If you think I should m...