ping, don't let this one die on me please :)
On Sun, May 21, 2017 at 7:05 PM, Martell Malone
wrote:
> ping :)
>
> On Thu, May 11, 2017 at 2:10 PM, Martell Malone
> wrote:
>
>> Thanks Kai,
>>
>> We probably don't need to push and pop because
Hi,
I am currently looking at emulating
_locale_t _get_current_locale(void);
We were previously hacking around this by just returning 0 cast as
_locale_t in msys2
This is obviously incorrect and any sane c++ tries to check multiple times
with that result.
What would be the correct way to
Following up with an initial patch
Not sure if this is ideal because this will be used over the MSVC version.
I can add it to a c source as an emulation if that suits better
diff --git a/mingw-w64-headers/crt/time.h b/mingw-w64-headers/crt/time.h
index 7f5bbb78..405a9f1d 100644
---
Thanks for that clarification Ricardo.
It seems that when we bumped we didn't bump far enough :)
Kai what are your thoughts?
On Sun, Jun 4, 2017 at 12:13 AM, Ricardo Constantino
wrote:
> On 3 June 2017 at 19:52, Mateusz Mikuła wrote:
>
> > 0x0502 is
On 3 June 2017 at 19:52, Mateusz Mikuła wrote:
> 0x0502 is Windows Server 2003
>
> If changing default target it should be done properly. Windows Vista is
> EOL and it's share is lower than XP so I'd vote for Windows 7.
>
>
> -- Original Message --
> Subject:
0x0502 is Windows Server 2003
If changing default target it should be done properly. Windows Vista is
EOL and it's share is lower than XP so I'd vote for Windows 7.
-- Original Message --
Subject: [Mingw-w64-public] Default _WIN32_WINNT version too low?
Date: Sat, 3 Jun 2017 18:27:40
Hey,
As per my discussion with LLVM devs here.
0x600 is the min version required to support libc++ win32 threading.
https://reviews.llvm.org/D33384
I'm not quite sure why we currently have 0x502 as the default.
It seems to be a number sitting between Windows XP and Vista.
I would like to propose
On 6/3/2017 12:22 PM, bob by wrote:
>
> Can you please tell how large C programs usually organize memory? Bunch of
> structures and globals I guess?
Yes. C is not Rust, it doesn't have an intricate memory ownership model. You
have chunks of memory and pointers to it. What you put there is up to
2017-06-02 17:30 GMT+04:00 LRN :
> On 6/2/2017 3:53 PM, bob by wrote:
> > On 2017-06-02 16:23 GMT+04:00 LRN wrote:
> >> On 6/2/2017 2:47 PM, bob by wrote:
> >>> Can somebody here write a replacement for the standard cout, that will
> be
> >>> able to print strings and integers,
2017-06-03 12:11 GMT+04:00 Mateusz Mikuła :
> Here is ios_base::Init https://github.com/gcc-mirror/
> gcc/blob/master/libstdc%2B%2B-v3/include/std/iostream#L74
> If you really want to understand what compiler put into your executable
> you have to disassemble it.
> Bear in mind
Pasted wrong link, here is fixed
https://github.com/gcc-mirror/gcc/blob/master/libstdc%2B%2B-v3/include/bits/ios_base.h#L601
On June 3, 2017 10:11:30 AM GMT+02:00, "Mateusz Mikuła"
wrote:
>Here is ios_base::Init
Here is ios_base::Init
https://github.com/gcc-mirror/gcc/blob/master/libstdc%2B%2B-v3/include/std/iostream#L74
If you really want to understand what compiler put into your executable you
have to disassemble it.
Bear in mind that even if you knew whole source code of libstdc++ you would get
2017-06-03 5:26 GMT+04:00 Liu Hao :
> On 2017/6/3 0:18, bob by wrote:
>
>> Can't find the code of std::ios_base::Init
>>
>> It should be somewhere in here, but I can't find it:
>> https://gcc.gnu.org/onlinedocs/gcc-6.3.0/libstdc++/api/a00801.html
>>
>> Why do you want to find
13 matches
Mail list logo