Chelsea Antiques Fair-2020

2020-02-10 Thread Jane Smith
Hi, Trust you are doing well. We take this opportunity to know if you would be interested in acquiring the Attendees & Exhibitors list of Chelsea Antiques Fair- 2020 At uk for pre-show marketing campaign, networking and various marketing initiatives The list contains: Company/Firm Name,

Re: Git ChangeLog policy for GCC Testsuite inquiry

2020-02-10 Thread Richard Biener
On Fri, Feb 7, 2020 at 4:43 PM Richard Earnshaw (lists) wrote: > > On 07/02/2020 15:32, Segher Boessenkool wrote: > > On Fri, Feb 07, 2020 at 01:56:08PM +, Richard Earnshaw (lists) wrote: > >> On 07/02/2020 13:48, Segher Boessenkool wrote: > >>> Should we require some simple markup in the comm

Re: Git ChangeLog policy for GCC Testsuite inquiry

2020-02-10 Thread Hans-Peter Nilsson
On Thu, 6 Feb 2020, Segher Boessenkool wrote: > Instead of "git am" I had "patch -p1 <", May I suggest "git apply" instead of the good old patch program. (The "-p1" is of course built-in and you never have to do a manual roll-back or separate --dry-run pass.) brgds, H-P

Re: Git ChangeLog policy for GCC Testsuite inquiry

2020-02-10 Thread Matthew Malcomson
On 08/02/2020 16:50, Segher Boessenkool wrote: On Fri, Feb 07, 2020 at 03:34:03PM -0700, Tom Tromey wrote: "Jason" == Jason Merrill writes: Jason> I omit ChangeLogs by adding ':!*/ChangeLog' to the end of the git Jason> send-email command. I don't remember where I found that incantation. Co

Request For Partnership

2020-02-10 Thread CLI INVESTMENT GROUP
Hello, CLI Investment Group here in New York, an affiliate of CLI Ventures. We are a Financial Investment Company looking for Company(s) with profitable projects or entrepreneurial teams that require partnership. We are focusing on supporting early to late stage Companies. If interested, please

Re: Git ChangeLog policy for GCC Testsuite inquiry

2020-02-10 Thread Segher Boessenkool
On Mon, Feb 10, 2020 at 05:51:10PM +, Matthew Malcomson wrote: > Just for anyone interested -- the manpage that describes the '!' is > `gitglossary`. > > It's under the description of `pathspec`, and has a long-form of > `:(exclude)`. https://github.com/git/git/commit/93dbefb389a011c9107a39

Eagerly evaluate __atomic_is_lock_free to 0 for oversized types

2020-02-10 Thread Fangrui Song
GCC never evaluates __atomic_is_lock_free to 0. (gcc/builtins.c:fold_builtin_atomic_always_lock_free) I'd like to change clang to eagerly evaluate __atomic_is_lock_free to 0 for apparently oversized types. This helps some platforms to avoid a dependency on libatomic. Either of the following cho

Re: Eagerly evaluate __atomic_is_lock_free to 0 for oversized types

2020-02-10 Thread Andrew Pinski
On Mon, Feb 10, 2020 at 8:35 PM Fangrui Song wrote: > > GCC never evaluates __atomic_is_lock_free to 0. > (gcc/builtins.c:fold_builtin_atomic_always_lock_free) Huh? /* We need a corresponding integer mode for the access to be lock-free. */ size = INTVAL (expand_normal (arg0)) * BITS_PER_UNI

Re: Eagerly evaluate __atomic_is_lock_free to 0 for oversized types

2020-02-10 Thread Andrew Pinski
On Mon, Feb 10, 2020 at 8:40 PM Andrew Pinski wrote: > > On Mon, Feb 10, 2020 at 8:35 PM Fangrui Song wrote: > > > > GCC never evaluates __atomic_is_lock_free to 0. > > (gcc/builtins.c:fold_builtin_atomic_always_lock_free) > > Huh? Oh it is this, you quoted the wrong function which made things