similar to: [LLVMdev] UBSan detects misaligned memory accesses in llvm-profdata and llvm-cov

Hi David, Vedant, It looks like we might have UB somewhere connected with reading coverage mapping serialized in v2 format (with compressed function names). I committed my patch, r266436, using the current format for .covmapping file, and then buildbots complained about it: * http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-fast/builds/11935/steps/check-llvm%20ubsan/logs/stdio *

Hello, Due the trees, I can't see the forest. I understand the concept of home directories on the file server becoming a share for the user on the smb-client computer. I have a vague idea of "profiles", but I'm lost at "profdata". How does that last one fit in? Where can I read more about it? (profdata is common keyword on the search engines) Is there a document

This week I migrated out main server from Fedora 8 to Fedora 11. It has been a stressful time, but things are mostly working. Samba and LDAP weren't really a problem, but I've beat down the list of problems to something Samba related. (For the benefit of anyone else going this route, the biggest problem by far was iptables. Maybe we had it turned off under FC8, but I suspect

Duncan, Justin, I'm about to submit a series of patches that add writing capabilities for sample profiles in both text and binary formats. Soon, I'll add a third format (to make it interoperable with GCC). I would like to add some profile maintenance utilities as well: merging, dumping and converting. It seems like the best place would be tools/llvm-profdata. But that means that I need

Hi Dennis! clang-x64-ninja-win7 fails for some time on 1. UNRESOLVED: UBSan-Standalone-x86_64::log-path_test.cc <http://lab.llvm.org:8011/builders/clang-x64-ninja-win7/builds/4522/steps/ninja%20check%201/logs/UNRESOLVED%3A%20UBSan-Standalone-x86_64%3A%3Alog-path_test.cc> this masks other new test failuers (clang modules related). Could you have a look? Yaron -------------- next

Wayne, I noticed that rsync's "*deleting" itemize output needs two trailing spaces now that the other itemize codes are 11 characters wide. See the patch below. Matt ------------- Index: log.c =================================================================== RCS file: /cvsroot/rsync/log.c,v retrieving revision 1.179 diff -u -r1.179 log.c --- log.c 10 Jul 2007 13:55:49

On 11 November 2011 02:33, Eli Friedman <eli.friedman at gmail.com> wrote: > It's a known issue that the x86 backend doesn't know how to generate > dynamic stack realignment code for functions using allocas outside the > entry block.  Don't know the bug number off the top of my head. These ones look relevant: http://llvm.org/bugs/show_bug.cgi?id=2962

Hi edA-qa mort-ora-y, On 12/05/13 17:13, edA-qa mort-ora-y wrote: > I'm trying to determine how to do my packed structure compilation and am > a bit unclear about how packed structures are handled. Consider this > structure: > > %struct.packed = type <{ i8, i32 }> > > Now if I get a pointer to the i32 element the pointer will not be > properly aligned for a

On 12/05/13 17:50, Duncan Sands wrote: > in LLVM, pointer types don't have an alignment associated with them. > Instead it is pointer operations that have an alignment (when relevant), > for example load and store instructions have an optional alignment. So > you need to put the alignment information onto the loads and stores that > you generate in your front-end. Okay, so I

Am 22.04.2016 um 12:40 schrieb g <geleem at bellsouth.net>: > greetings. > > centos 6.7 [current] > > > 'disk utility' has started showing message; > > WARNING: The partition is misaligned by 2560 bytes. This may > result in very poor performance. Repartitioning is suggested. > > for sdc5 - /home partition. > > /dev/sdc5 302243312

On 04/22/16 05:40, g wrote: <> > suggestions for correcting above boundaries also appreciated. > > help needed and greatly appreciated. > ===> thank you all for replies. most helpful. now to decide which way to format a new drive that i now have on order. after reading replies, i feel easiest way to get a good partition layout was a complete repartitioning and formatting.

On 04/22/2016 09:43 AM, g wrote: > ]$ sudo blockdev --getalignoff /dev/sdc1 > 0 > ]$ sudo blockdev --getalignoff /dev/sdc2 > 0 > ]$ sudo blockdev --getalignoff /dev/sdc5 > 2560 > ]$ sudo blockdev --report /dev/sdc1 > RO RA SSZ BSZ StartSec Size Device > rw 256 512 4096 2048 838860800 /dev/sdc1 > ]$ sudo blockdev --report

Hello, I recently noticed a small bug in the doveadm table formatter: hidden titles may cause the headers to be misaligned. The behavior in question was introduced by commit <http://hg.dovecot.org/dovecot-2.2/rev/210282ae46e1> and doveadm -f table quota get -A may be used to reproduce it. Most simple patch attached: it simply restores the old behavior, to some extent. Actually hiding

I haven't tested it, but it looks to me like llvm-profdata merge (well, InstrProfWriter specifically) would not have deterministic output. Certainly the textual output iterates over FunctionData which is a StringMap of SmallDenseMaps, neither of which has deterministic iteration. The binary writing looks like it'd have similar issues - looping through these unordered maps & writing

Hi! I'm trying to build a fast Clang for myself to use for debug builds on Clang itself, but I've been struggling for a very long time on it. Could you please help? I've been following this guide: https://llvm.org/docs/HowToBuildWithPGO.html I've quickly learned that its outdated, because the script it talks about doesn't work with the monorepo layout at all, but in any

I'm trying to determine how to do my packed structure compilation and am a bit unclear about how packed structures are handled. Consider this structure: %struct.packed = type <{ i8, i32 }> Now if I get a pointer to the i32 element the pointer will not be properly aligned for a typical i32. On my current machine (x86_64) the cpu doesn't seem to care, but I suspect this isn't

On Thu, Nov 10, 2011 at 6:13 PM, Aaron Dwyer <Aaron.Dwyer at imgtec.com> wrote: > Using LLVM 2.9, the following LLVM IR produces invalid x86 32 bit assembly > (a misaligned SSE store). > ; ModuleID = 'MisalignedStore' > define void @MisalignedStore() nounwind readnone { > entry: >   %v = alloca <4 x float>, align 16 >   store <4 x float>

I am running a 3-parameter nonlinear fit using the default Gauss-Newton method of nls. initialValues.L = list(b=4,d=0.04,t=180); fit.nls.L = nls( myModel.nlm , fData.L, start = initialValues.L, control = nls.control(warnOnly = TRUE), trace=T ); summary.nls.L = summary(fit.nls.L); I run the same analysis in SAS proc NLIN. proc nlin data=apples outest=a; parms b=4 d=.04 t=180; model Y =

On 04/22/16 08:19, Leon Fauster wrote: <<>> > check it with: > > blockdev --getalignoff /dev/sd > > (if a '0' is returned, the partition is aligned) > ===> Leon, thank you for reply. ]$ sudo blockdev --getalignoff /dev/sdc1 0 ]$ sudo blockdev --getalignoff /dev/sdc2 0 ]$ sudo blockdev --getalignoff /dev/sdc5 2560 ]$ sudo blockdev --report /dev/sdc1 RO

Using LLVM 2.9, the following LLVM IR produces invalid x86 32 bit assembly (a misaligned SSE store). ; ModuleID = 'MisalignedStore' define void @MisalignedStore() nounwind readnone { entry: %v = alloca <4 x float>, align 16 store <4 x float> zeroinitializer, <4 x float>* %v, align 16 br label %post-block post-block: %f = alloca float ret void } If I feed