- Niuce C++14-feature - 22 Updates
- I/O-benchmark - 2 Updates
- Why does this work in MSVC 2019... - 1 Update
| Bonita Montero <Bonita.Montero@gmail.com>: May 19 01:11PM +0200 > Thanks for your input sock puppet. I'm posting here for years and I'm no one's sock puppet. > Just because you can't find it in google doesn't mean it doesn't exist. Such a common bug wouuld be documented and could be found with Google or whatever if it really existed, Mr. Liar. |
| MrSpook_a9r7@vdgtzl3x.gov.uk: May 19 11:19AM On Wed, 19 May 2021 13:11:08 +0200 >> Just because you can't find it in google doesn't mean it doesn't exist. >Such a common bug wouuld be documented and could be found with >Google or whatever if it really existed, Mr. Liar. Why would the bug mailing list for suns C++ compiler from the late 90s be indexed on google? |
| Bonita Montero <Bonita.Montero@gmail.com>: May 19 01:33PM +0200 >> Google or whatever if it really existed, Mr. Liar. > Why would the bug mailing list for suns C++ compiler from the late 90s be > indexed on google? Because such contents would be available today. My postings of the late 90s are also all available today. |
| Juha Nieminen <nospam@thanks.invalid>: May 19 12:01PM > stronger? Think of a troll as a prototype for the proverbial Cruel Puppet: > https://www.thezorklibrary.com/history/cruel_puppet.html > Fair enough? Ok, I'll stop. |
| Manfred <noname@add.invalid>: May 19 03:16PM +0200 On 5/19/2021 7:02 AM, Juha Nieminen wrote: >> What I gain is not seeing any more of your posts, with a resulting >> improvement in the signal-to-noise ratio of my view of the newsgroup. > Of an almost dead newsgroup at that. And then why do you post here? > always been. There is no moderation, and that's probably one of the > reasons why it's almost dead and the vast majority of companies and > service providers have dropped support. You know that your recent deliberately insulting posts would have been blocked by any decent moderator, right? |
| MrSpook_of0j0vqHff@bap.com: May 19 01:29PM On Wed, 19 May 2021 13:33:11 +0200 >> indexed on google? >Because such contents would be available today. >My postings of the late 90s are also all available today. Do you know the difference between public usenet postings and a mailing list? You know what, I can't be bothered to argue over this trivial issue. If for some bizarre reason you won't except that some 20+ year old C++ compiler had a trivial bug then fine, don't, I really don't bloody care. |
| James Kuyper <jameskuyper@alumni.caltech.edu>: May 19 10:07AM -0400 On 5/19/21 1:02 AM, Juha Nieminen wrote: >> What I gain is not seeing any more of your posts, with a resulting >> improvement in the signal-to-noise ratio of my view of the newsgroup. > Of an almost dead newsgroup at that. Google no longer provides message counts by newsgroup in any place I could easily find. However, dozens of threads have had hundreds of messages added to them in this newsgroup during this month alone. That's less than the peak activity level for this newsgroup, but it's not enormously smaller than that peak, either. I will grant you that most of those messages were posted by people I've got killfiled - the number of messages worth reading is much smaller than the number posted - but that's always been the case. > On that note, I honestly could not care less what you personally > find "unacceptable" on usenet. Why should that matter? Keith's killfile is for Keith, not you. If he finds your behavior unacceptable, then that's all the justification HE needs for making sure that he no longer sees it. |
| Bonita Montero <Bonita.Montero@gmail.com>: May 19 04:17PM +0200 > Do you know the difference between public usenet postings and a mailing > list? You can even read Linux mailinglists from the beginning of the 90s, Mr. Liar. |
| James Kuyper <jameskuyper@alumni.caltech.edu>: May 19 10:20AM -0400 > I'm curious as to why you think someone criticising an aspect of C++ > is trolling. If this forum is merely to praise how wonderful the language > is to its acolytes then what purpose does it serve? Trolling is defined as intentionally posting an upsetting message for the purpose of triggering a response, rather than a serious attempt to discuss the issue. It comes from the practice of trolling for fish, with the triggered response considered to be analogous to the fish going for your bait. Most trolling is also criticism. Whether any given piece of criticism is also a troll is often a very subjective judgement call, and if you honestly don't already recognize this particular criticism as trolling, I can't imagine what I could say to change your mind, so I won't bother trying. |
| James Kuyper <jameskuyper@alumni.caltech.edu>: May 19 10:34AM -0400 On 5/19/21 5:16 AM, David Brown wrote: > On 18/05/2021 17:35, MrSpook_h2j5v@jq7cn18h8lm.com wrote: ... > A virtual function is syntactic sugar for a function pointer (in a > table). The syntax " = 0" for a pure virtual function is then obvious - > it is initialising the function pointer to a null pointer. The key point, which no one seems to have stated explicitly, is that using anything other than 0 in this location constitutes a syntax error. A pure specifier is optional, but the only permitted form for a pure-specifier is "= 0". It's unambiguously a diagnosable rule, the violation of which requires a diagnostic message. Any decent compiler will generate such a diagnostic. It's certainly possible for a compiler to have a bug in it that would cause it to crash rather than generate that diagnostic, so the claim that MrSpook must be lying is unjustified. But I do think it an implausible type of bug. |
| MrSpook_g1@mpi.com: May 19 02:55PM On Wed, 19 May 2021 10:34:03 -0400 >to have a bug in it that would cause it to crash rather than generate >that diagnostic, so the claim that MrSpook must be lying is unjustified. >But I do think it an implausible type of bug. Most bugs are fairly implausible but they happen. It was a real bug. Its possible the compiler has some extension that allowed a non zero value to be assigned, perhaps a function pointer so anything non zero would be treated as an address. Thats a guess, I have no idea. Regardless it crashed quite spectacularly IIRC , not a segfault but an internal stack dump. |
| MrSpook_83b6en@o2cr9.ac.uk: May 19 02:57PM On Wed, 19 May 2021 16:17:45 +0200 >> Do you know the difference between public usenet postings and a mailing >> list? >You can even read Linux mailinglists from the beginning of the 90s, I imagine the linux mailing lists were public. The sun ones would have been probably have been restricted to customers. The Sun compiler was paid for back then. >Mr. Liar. This is you I presume? https://stackoverflow.com/users/6469690/bonita-montero Your name is a lie. |
| Bonita Montero <Bonita.Montero@gmail.com>: May 19 05:49PM +0200 > I imagine the linux mailing lists were public. The sun ones would have > been probably have been restricted to customers. The Sun compiler was paid > for back then. Please proved the paid mailing-lists ... > This is you I presume? > https://stackoverflow.com/users/6469690/bonita-montero That'S me. |
| Bonita Montero <Bonita.Montero@gmail.com>: May 19 06:13PM +0200 Trolling is when the provocation ends in itself and is not rooted in the real opinions of the trolls. There might be idiots with strange attitudes which might be provocating #that they seem to be trolling - but the stand behind their stupid opinions and thereby arent really trolls. Maybe MrSpook is such a stupid person. |
| Mr Flibble <flibble@reddwarf.jmc>: May 19 04:15PM On Wed, 19 May 2021 14:55:09 +0000, MrSpook_g1 wrote: > treated as an address. Thats a guess, I have no idea. Regardless it > crashed quite spectacularly IIRC , not a segfault but an internal stack > dump. This is a classic case of first trying to explain away a basic mistake that you aren't man enough to admit to and then an attempt to backtrack. No, no C++ compiler has ever used the pure specifier as a function pointer. /Flibble |
| Keith Thompson <Keith.S.Thompson+u@gmail.com>: May 19 10:09AM -0700 > I'm curious as to why you think someone criticising an aspect of C++ > is trolling. If this forum is merely to praise how wonderful the language > is to its acolytes then what purpose does it serve? I don't, and it isn't. I've simply chosen to update my killfile (actually a Gnus score file) to improve the signal-to-noise ratio of my personal view of this newsgroup. If you wish to discuss it further, my email address is valid. -- Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com Working, but not speaking, for Philips Healthcare void Void(void) { Void(); } /* The recursive call of the void */ |
| scott@slp53.sl.home (Scott Lurndal): May 19 05:41PM >> been probably have been restricted to customers. The Sun compiler was paid >> for back then. >Please proved the paid mailing-lists ... Your grammar is lacking here, I assume you're requesting that the poster, who's attribution _YOU REMOVED FROM YOUR REPLY_ prove that Solaris mailing lists were restricted to Sun Customers? That was always the case for Solaris, later when OpenSolaris was introduced, access to some information was eased (but there were two communities, the Solaris and the OpenSolaris, each with different support structures). >> This is you I presume? >> https://stackoverflow.com/users/6469690/bonita-montero >That'S me. You have slipped a few times and posted under your real name Christopher aus Deutschland. |
| Bonita Montero <Bonita.Montero@gmail.com>: May 19 07:55PM +0200 > You have slipped a few times and posted under your real > name Christopher aus Deutschland. I'm not aware of whom you're talking about. But it's correct I'm from Germany. |
| "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com>: May 19 01:33PM -0700 On 5/19/2021 3:57 AM, Bonita Montero wrote: > No one needs pure futexes - they're used to build other synchronization > -facilities on top of them. Some of them are those you have in mind wich > could be used to emulate a futex. Right. However, it can be a fun exercise to emulate them in pure C/C++ using atomics, membars, and condvars. However, the emulated futex cannot be used for interprocess work, only intraprocess. |
| "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com>: May 19 01:39PM -0700 >> can be emulated as well. in C++11. > Oh ok. So explain how you'd implement an atomic futex in userspace that say > was used to implement a semaphore that other processes would use. Oh, I cannot do that in pure C/C++. Only Intraprocess. >> code shall run. > No, it wouldn't. Real time compilers often only support a subset of a language > whether it be C or C++. If a compiler says it supports C/C++11, then C/C++11 code should run on it? >> Windows has nothing to do with it. > What is the reason then? I am not exactly sure what you mean, but Windows has a futex like mechanism. I cannot remember if they can be used for interprocess communication: https://docs.microsoft.com/en-us/windows/win32/api/synchapi/nf-synchapi-waitonaddress |
| "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com>: May 19 01:46PM -0700 On 5/19/2021 1:39 PM, Chris M. Thomasson wrote: >> that say >> was used to implement a semaphore that other processes would use. > Oh, I cannot do that in pure C/C++. Only Intraprocess. [...] Iirc, I did one a while back, before C/C++11 that hashed a pointer into a table of mutexes and condvars that was used as the addresses waitset. Iirc, I called that part of it a multimutex: https://groups.google.com/g/comp.lang.c++/c/sV4WC_cBb9Q/m/Ti8LFyH4CgAJ |
| "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com>: May 19 01:54PM -0700 On 5/19/2021 4:33 AM, Bonita Montero wrote: >> indexed on google? > Because such contents would be available today. > My postings of the late 90s are also all available today. Well, I won a brand new SunFire T2000 from the CoolThreads contest, but I cannot find the proof on Google right now. Iirc is on the waybackmachine. Here is an old post about the contest: https://www.webwire.com/ViewPressRel.asp?aId=6542 My project was called vZOOM. Wait a minute, I found it: https://web.archive.org/web/20070620081114/https://coolthreads.dev.java.net/ Look for vzoom, that's me! |
| scott@slp53.sl.home (Scott Lurndal): May 19 02:05PM >1024 9271 >As you can see, the 10 years oder processor with 1/16-the of number >of cores is faster up to 8kB block-size. For your comparison to be valid requires a single point of difference. You have at least five points of difference; a different operating system, a different compiler, a different processor, a different I/O controller and a different storage device. It's likely that the prime difference is that Linux has a much better I/O subsystem that Windows. |
| Bonita Montero <Bonita.Montero@gmail.com>: May 19 05:53PM +0200 > a different operating system, a different compiler, a different > processor, a different I/O controller and a different storage > device. The compiler doesn't matter. The code performs according to the efficiency of the operating-system. The I/O-controller doesn't matter since I asked for repeated results from the cache. But it does matter to compare different CPUs with different operating-systems. I compared a Phenom X4 945 4-core with a Ryzen Threadripper 3900X 64-core and the first one is faster up to a block-size of 8kB. And as this is mostly rooted in the efficiency of the operating-system because the Phenom is par- tititally faster. > It's likely that the prime difference is that Linux has a much > better I/O subsystem that Windows. Of course - and kernel-calls are supposed to be more efficient. |
| James Kuyper <jameskuyper@alumni.caltech.edu>: May 19 09:58AM -0400 On 5/19/21 1:57 AM, Christian Gollwitzer wrote: ... > You are basically accessing memory that was "freed"[*] before. That is ... > [*] not on the heap, so not "malloc/free-type freed", but "stack-freed" I have not bothered checking his code to verify that your diagnosis is correct. However, if it is, the correct way to describe your diagnosis is to say that his code attempts to access the value stored in an object after the lifetime of that object has ended. That description covers both dynamically allocated objects that have been deallocated, and automatic objects after the block in which they are defined exits. |
| You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page. To unsubscribe from this group and stop receiving emails from it send an email to comp.lang.c+++unsubscribe@googlegroups.com. |
No comments:
Post a Comment