search for: hasflag

...`-target -i386`, >which is a triple with no OS, so Clang is doing something arbitrary. Grepping >Clang sources shows that this flag is handled in an OS-specific manner: > >$ git grep -i fuse_init_array ../clang/lib/Driver/ >../clang/lib/Driver/ToolChains/Fuchsia.cpp:  if (DriverArgs.hasFlag >(options::OPT_fuse_init_array, >../clang/lib/Driver/ToolChains/Gnu.cpp:  if (DriverArgs.hasFlag >(options::OPT_fuse_init_array, >../clang/lib/Driver/ToolChains/NetBSD.cpp:  if (DriverArgs.hasFlag >(options::OPT_fuse_init_array, >../clang/lib/Driver/ToolChains/WebAssembly.cpp:  if...

...// unsafe bits of "dest" + source.window = window; + source.frame = frame; + source.buttons = buttons; + // now assign + *this = source; + } + + bool IsOk() const { return (window != NULL) ? true : false; } + bool IsFixed() const { return !HasFlag(optionResizable); } + bool IsResizable() const { return HasFlag(optionResizable); } + bool IsShown() const { return !HasFlag(optionHidden); } + bool IsFloating() const { return HasFlag(optionFloating); } + bool IsDocked() const { return !HasFlag(optionFloating); } + bool IsToolbar()...

Hi Devs, consider below testcases, $cat test.cc class B { public: B(int t) { j=t; } int j; }; B b(1); ============== $clang test.cc -target -i386 -c -fuse-init-array $llvm-objdump -h test.o |grep ctors 7 .ctors 00000004 00000000 DATA 8 .rel.ctors 00000008 00000000 As you can see it ignores the -fuse-init-array options.It happens for x86,Other target like aarch64 is doing fine.

I've come across a need to know whether an option was set true, false or unspecified. If it is true I want to do one thing, if it is false I want to do something else and if it is unspecified I want to do nothing. ArgList::hasFlag is a convenient way to check true/false with a default value. An ArgList::hasFlag that returned Optional<bool> would allow checking the unspecified case. Returning some kind Tribool class object would allow the same. Both Optional<bool> and Tribool are somewhat overkill for this kind...

No, I’m wrong. I think that bug is actually in ‘hasFlag’ itself. In ‘llvm/lib/Option/ArgList.cpp’ line #70: bool ArgList::hasFlag(OptSpecifier Pos, OptSpecifier PosAlias, OptSpecifier Neg, bool Default) const { if (Arg *A = getLastArg(Pos, PosAlias, Neg)) return A->getOption().matches(Pos) || A->...

...7 To: 'Richard Smith' <richard at metafoo.co.uk>; 'Clang Dev' <cfe-dev at lists.llvm.org> Cc: 'LLVM Developers' <llvm-dev at lists.llvm.org> Subject: RE: [cfe-dev] Disabling vectorisation at '-O3' No, I’m wrong. I think that bug is actually in ‘hasFlag’ itself. In ‘llvm/lib/Option/ArgList.cpp’ line #70: bool ArgList::hasFlag(OptSpecifier Pos, OptSpecifier PosAlias, OptSpecifier Neg, bool Default) const { if (Arg *A = getLastArg(Pos, PosAlias, Neg)) return A->getOption().matches(Pos) || A->...

...ghtened me. Any advice for how I can > > accomplish this? > > Off of the top of my head... > > Within the current infrastructure, I think that we need to alter the Clang PowerPC toolchain code (Clang::AddPPCTargetArgs in Tools.cpp) to do something like this: > > if (Args.hasFlag(options::OPT_fno_altivec, options::OPT_faltivec, true)) { > CmdArgs.push_back("-backend-option"); > CmdArgs.push_back("-mattr=-altivec"); > } Perfect, Hal, thanks! That makes good sense. I'll fix this and also bring some of the CPU handling more up-to-date (s...

...his? > > > > > > Off of the top of my head... > > > > > > Within the current infrastructure, I think that we need to alter the Clang PowerPC toolchain code (Clang::AddPPCTargetArgs in Tools.cpp) to do something like this: > > > > > > if (Args.hasFlag(options::OPT_fno_altivec, options::OPT_faltivec, true)) { > > > CmdArgs.push_back("-backend-option"); > > > CmdArgs.push_back("-mattr=-altivec"); > > > } > > > > Perfect, Hal, thanks! That makes good sense. I'll fix this and also...

...an > > > accomplish this? > > > > Off of the top of my head... > > > > Within the current infrastructure, I think that we need to alter the Clang PowerPC toolchain code (Clang::AddPPCTargetArgs in Tools.cpp) to do something like this: > > > > if (Args.hasFlag(options::OPT_fno_altivec, options::OPT_faltivec, true)) { > > CmdArgs.push_back("-backend-option"); > > CmdArgs.push_back("-mattr=-altivec"); > > } > > Perfect, Hal, thanks! That makes good sense. I'll fix this and also > bring some of the C...

...> > > Off of the top of my head... > > > > > > > > Within the current infrastructure, I think that we need to alter the Clang PowerPC toolchain code (Clang::AddPPCTargetArgs in Tools.cpp) to do something like this: > > > > > > > > if (Args.hasFlag(options::OPT_fno_altivec, options::OPT_faltivec, true)) { > > > > CmdArgs.push_back("-backend-option"); > > > > CmdArgs.push_back("-mattr=-altivec"); > > > > } > > > > > > Perfect, Hal, thanks! That makes good sense. I...

I've created a new clang option for my target through Options.td. Is there a way to give it a default value? -- Rail Shafigulin Software Engineer Esencia Technologies -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160608/0f7ba340/attachment.html>

...eflag", and "removeflag" Actions Implementations of IMAP events in Sieve MUST also support the imap4flags extension [RFC5232], and the actions associated with it are all applicable to any case that falls under IMAP events in Sieve. It is worth noting also that the "hasflag" test that is defined in the imap4flags extension might be particularly useful in scripts triggered by flag changes ("hasflag" will see the new, changed flags). The flag changes behave as though a client had made the change. As explained above, in order to avoid scri...

...from other targets hasn't enlightened me. Any advice for how I can > accomplish this? Off of the top of my head... Within the current infrastructure, I think that we need to alter the Clang PowerPC toolchain code (Clang::AddPPCTargetArgs in Tools.cpp) to do something like this: if (Args.hasFlag(options::OPT_fno_altivec, options::OPT_faltivec, true)) { CmdArgs.push_back("-backend-option"); CmdArgs.push_back("-mattr=-altivec"); } Why this not done currently I don't know. -Hal > > Thanks! I appreciate any help. > > Bill > > -- > Bill S...

Yes, it looks like passing ‘EnableVec’ and ‘EnableSLPVec’ to ‘Args.hasFlag’ should be replaced with ‘false’ and then it has the expected behaviour. MartinO From: cfe-dev [mailto:cfe-dev-bounces at lists.llvm.org] On Behalf Of Martin J. O'Riordan via cfe-dev Sent: 01 March 2018 18:02 To: 'Richard Smith' <richard at metafoo.co.uk> Cc: &...

...g" Actions > > Implementations of IMAP events in Sieve MUST also support the > imap4flags extension [RFC5232], and the actions associated with it > are all applicable to any case that falls under IMAP events in Sieve. > > It is worth noting also that the "hasflag" test that is defined in > the imap4flags extension might be particularly useful in scripts > triggered by flag changes ("hasflag" will see the new, changed > flags). The flag changes behave as though a client had made the > change. > > As expla...

The problem I'm trying to solve: Invoking clang on PowerPC with -fno-altivec has no effect. >From what I've been able to piece together, PPC.td specifies various CPUs and the processor features available on each. So for example we have: def FeatureAltivec : SubtargetFeature<"altivec","HasAltivec", "true",

I tried with following: require ["imap4flags"]; if not hasflag :is "\\Seen" { setflag "\\Seen"; } And then this in plugins.conf: plugin { sieve_plugins = sieve_imapsieve imapsieve_mailbox1_name = Trash imapsieve_mailbox1_before = file:/etc/dovecot/sieve/trash.sieve } It works in outlook, the mail is opened (mark as read) when it go...

Dovecot version: 2.3.7.2 (3c910f64b) (pkg shipped by: Ubuntu-Desktop 20.04) I want to accomplish 2 things in dovecot: 1: I want to force all mails inside Trash to have an "opened"/"read" flag and "Non-Recent" flag. Basically Status: RO This regardless how the flag appears, either by copying/moving the mail into trash, creating a new mail in trash, flagging email in

Hi everybody, As you know, Cuda/NVPTX target has very limited support of the debug info in Clang/LLVM. Currently, LLVM supports only emission of the line numbers debug info. This is caused by limitations of the Cuda/NVPTX codegen. Clang/LLVM translates the source code to LLVM IR, which is then lowered to PTX (parallel thread execution) intermediate file. This PTX file represents special kind of

Using `fileinto` to move a mail into another mailbox removes flags that have been set with a previous sieve filter with `addflag`. # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 4.9.0-6-amd64 x86_64 Debian 9.1 ext4 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_debug = yes mail_location = maildir:/var/vmail/%d/%n