search for: newattr

Hi All, I need your guidance about a custom attribute. I have defined one for variables. It is accepted in the source code (without any warnings from clang), for example in following snippet. #define NEWATTR __attribute__((moviAttr(1))) int main() { NEWATTR volatile unsigned int a = 5; volatile unsigned int *p; p = &a; return (a+*p); } and actually when I Dump the declaration, after adding the attribute in handleMoviAttr() function in SemaDeclAttr.cpp as shown in following snippet D->a...

...e is correct, since clang doesnt generate any error. do you think there is anyother reason for my custom attribute to not appear in IR? --- Naveed Ul Mustafa On 2016-11-25 13:44, Asit Dhal wrote: > Hi, > > I think, the syntax is wrong. > You can try this way.. > > #DEFINE NEWATTR __ATTRIBUTE__((ANNOTATE("MOVIATTR"))) > > int main() > { > NEWATTR volatile unsigned int a = 5; > VOLATILE UNSIGNED INT *P; > p = &a; > return (a+*p); > } > > And it generates > > ; ModuleID = 'test2.cpp' &...

...>> appear in IR? >> >> >> >> --- >> Naveed Ul Mustafa >> >> On 2016-11-25 13:44, Asit Dhal wrote: >> > Hi, >> > >> > I think, the syntax is wrong. >> > You can try this way.. >> > >> > #DEFINE NEWATTR __ATTRIBUTE__((ANNOTATE("MOVIATTR"))) >> > >> > int main() >> > { >> > NEWATTR volatile unsigned int a = 5; >> > VOLATILE UNSIGNED INT *P; >> > p = &a; >> > return (a+*p); >> > } &g...

...s cleared. Please look at rsync-3.1.0/rsync.c lines 492 & 541 in the context of chown_common() from linux kernel fs/open.c around the 500th line. It appears that the SET{G,U}ID bits and security attrs are cleared. Relevant kernel line: if (!S_ISDIR(inode->i_mode)) newattrs.ia_valid |= ATTR_KILL_SUID | ATTR_KILL_SGID | ATTR_KILL_PRIV; Suggestion: move the SUPPORT_XATTRS code invocation after the if (change_uid... block. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ---...

...int presto_do_truncate(struct presto_file_set *fset, struct dentry *dentry, loff_t length, loff_t size_check) { struct inode *inode = dentry->d_inode; struct super_operations *op; int error; struct iattr newattrs; ENTRY; /* Not pretty: "inode->i_size" shouldn't really be "loff_t". */ if ((off_t) length < 0) return -EINVAL; down(&inode->i_sem); if (size_check != inode->i_size) { up(&inode...

i_alloc_sem has always been a bit of an odd "lock". It''s the only remaining rw_semaphore that can be released by a different thread than the one that locked it, and it''s use case in the core direct I/O code is more like a counter given that the writers already have external serialization. This series removes it in favour of a simpler counter scheme, thus getting rid