search for: snooti

On Tue, Aug 15, 2017 at 9:37 PM, Tim Northover via cfe-dev < cfe-dev at lists.llvm.org> wrote: > On 15 August 2017 at 19:38, bharathi seshadri via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > I find that GCC has an option -fno-tree-loop-distribute-patterns that > > can be used to disable memcpy/memset synthesis. I wonder if there is > > something similar

My concern wasn't a phylosophical one but a pragmatic one. Learning about poor choices when lowering memset is probably quite useful. Having a flag that just turns off idiom recognition for it may just work around the problem. But the problem may still exist. In any case, I'm not fundamentally against such a flag but it just seems like something that could 1. Hide a problem 2. Get a bit

I thought more about this last night after my email about putting an end to "Read the Manual" replies. It seems that there are a handful of R Super-Programmers. If I were one, I would get tired of 100's of questions like "How can I get my Excel file into R!!!". Concurrently, R is experiencing an exponential increase in new users to the extent that there are now

Hello I assume I'm not the first one to think about this: Is it possible to connect an intercom and/or door bell to Asterisk, so that I can get an e-mail that someone rang my place while I was out? Even better: If used for a doctor's office, it'd be cool if patients could type their Social Security Number on a keypad, which would open the door and notify Asterisk which would then

I have a semi-grand plan for some changes to migrations. Mostly this is motivated by the upcoming 3.0 release and wanting to get migrations in engines working. 1. Don''t skip migrations with version numbers lower than "current". I only recently tripped over this, but apparently it''s been this way since 2.1 when we got timestamps masquerading as large/sparse