Re: [Mingw-w64-public] Various std::experimental::filesystem errata

2017-07-03 Thread Riot
.cpp -lstdc++fs #include auto main()->int { std::experimental::filesystem::remove("my_file.txt"); return EXIT_SUCCESS; } terminate called after throwing an instance of 'std::experimental::filesystem::v 1::__cxx11::filesystem_error' what(): filesystem error: cannot remove

[Mingw-w64-public] Various std::experimental::filesystem errata

2017-07-03 Thread Riot
to delete anything. Regards, Riot -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Mingw-w64-publ

Re: [Mingw-w64-public] Default _WIN32_WINNT version too low?

2017-06-12 Thread Riot
;s working fine, and removing which doesn't benefit anyone. On 12 June 2017 at 19:01, Riot wrote: > Haha, no - although I do work for a game company, I'd rather not say which > on-list. > > Am I mistaken in that the patch affects the CRT? In which case, defining > _WIN

Re: [Mingw-w64-public] Default _WIN32_WINNT version too low?

2017-06-12 Thread Riot
ption for us with our current build pipeline, as we rely on mingw-builds currently. Any change to the default would leave us in future with a toolchain unable to build for mingw-w64. Regards, Riot On 12 June 2017 at 18:46, David Grayson wrote: > Riot, do you work for Riot Games? > > A

Re: [Mingw-w64-public] Default _WIN32_WINNT version too low?

2017-06-12 Thread Riot
t see this as a constructive change, as it doesn't appear to actually improve anything for anybody. Can we reconsider? Regards, Riot On 12 June 2017 at 18:02, Liu Hao wrote: > On 2017/6/12 23:17, Martell Malone wrote: > >> In that case, >> I think the best course of im

Re: [Mingw-w64-public] Erroneous "out of memory" using LTO

2017-03-14 Thread Riot
for us - do you happen to know if anyone is building such a thing regularly and where? Regards, Riot On 14 March 2017 at 22:56, Ruben Van Boxem wrote: > The default values can be found in > https://github.com/gcc-mirror/gcc/blob/master/gcc/params.def > > For example, but I guess you

Re: [Mingw-w64-public] Erroneous "out of memory" using LTO

2017-03-14 Thread Riot
ng wrong that's causing this behaviour. I may have worked around the possible bug by disabling the option, but that doesn't address the root cause. Are you saying that this is a user error and using `max-inline-insns-auto=1` is unsupported, and the compiler is expected to sometimes

Re: [Mingw-w64-public] Erroneous "out of memory" using LTO

2017-03-13 Thread Riot
est further, I can do - just let me know. Regards, Riot On 13 March 2017 at 16:01, Ruben Van Boxem wrote: > Hi, > > Just some random helpful thoughts: > - the linker typically uses a lot more memory than the sum of everything it > is linking together. > - LTO is still quite

[Mingw-w64-public] Erroneous "out of memory" using LTO

2017-03-13 Thread Riot
ference. We haven't encountered this problem building the same project with the same settings natively on GCC under Linux or on MacOS. Any help would be much appreciated! Regards, Riot -- Announcing the Oxford Diction

Re: [Mingw-w64-public] Help building cross-compiler on Linux

2016-12-12 Thread Riot
all would be appreciated. If I've gone wrong somewhere earlier along the line, and could have avoided all the 32bit/64bit makefile fiddling, I would also love to hear how, as I doubt that the above is how it's supposed to proceed. Regards, Riot ... On 7 December 2016 at 23:25, JonY w

[Mingw-w64-public] Help building cross-compiler on Linux

2016-12-07 Thread Riot
hrough comprehensively all the steps required from download through to successful configure, or point me to some up to date docs I may have missed that outline these. Thanks, Riot -- Developer Access Program for Intel

Re: [Mingw-w64-public] sinl/cosl/tanl accuracy problem

2016-09-07 Thread Riot
itch would be a way to please everyone here? Regards, Riot On 7 September 2016 at 16:21, lhmouse wrote: > (I don't write AT&T assembly so I am unable to make a patch. > Nevertheless I hope someone who writes AT&T assembly could fix it.) > > The x87 `sinl` instruction

Re: [Mingw-w64-public] Moving sources from SourceForge to something better

2016-08-04 Thread Riot
Seconded. On Aug 5, 2016 1:02 AM, "Edward Diener" wrote: > Please, please consider moving mingw-64 sources from SourceForge to some > better hosting server. SourceForge has morphed into a real disaster > where downloading files from it are met by numerous tactics of delay and > failure to force

Re: [Mingw-w64-public] How the program is runing in windowsxp?

2016-04-12 Thread Riot
on XP, what error occurs? Are there any particular libraries you're using that might be causing the problem? -Riot On 11 April 2016 at 20:43, Pavel wrote: > Hello, > > I think this is not sufficient. -D__USE_MINGW_ANSI_STDIO should help, > however, my experience is that it

[Mingw-w64-public] Status of Cilk Plus support?

2015-08-13 Thread Riot
is there a MinGW compatible build of the library somewhere? I've been unable to find one myself. Regards, Riot -- ___ Mingw-w64-public mailing list Mingw-w64-p

Re: [Mingw-w64-public] Linker problem with i686-5.1.0-posix-dwarf-rt_v4-rev0 version

2015-07-24 Thread Riot
y 2015 at 16:03, Edward Diener wrote: > On 7/24/2015 8:54 AM, Riot wrote: > > Where are you defining your template, in the header or the source? You > > may need to explicitly instantiate. > > The template is being defined in the YY.cpp source file. > > > >

Re: [Mingw-w64-public] Linker problem with i686-5.1.0-posix-dwarf-rt_v4-rev0 version

2015-07-24 Thread Riot
Where are you defining your template, in the header or the source? You may need to explicitly instantiate. On 24 Jul 2015 13:31, "Edward Diener" wrote: > Before attempting to reduce my code to a small enough example to post > here in its entirety I will give a description of the problem to see if

Re: [Mingw-w64-public] [[deprecated]]

2015-07-15 Thread Riot
Use -std=gnu++1y On 16 Jul 2015 00:09, "Hotmail (ArbolOne)" wrote: > C++14 includes the [[deprecated("reason")]] attribute, but in my > MinGW-64 with GCC-5.1 it creates a warning saying: > warning: 'deprecated' attribute directive ignored [-Wattributes]| > > How can I find out which features of

Re: [Mingw-w64-public] C++14

2015-07-08 Thread Riot
I can confirm that __attribute__((deprecated("reason"))) definitely works on mingw-w64 with -std=gnu++1y, and probably with some others. On 8 July 2015 at 15:06, Ruben Van Boxem wrote: > Here you can find GCC's C++11 implementation status: > https://gcc.gnu.org/projects/cxx0x.html > > And the sa

Re: [Mingw-w64-public] toUpper()

2015-06-30 Thread Riot
#include #include std::string str = "Hello World"; std::transform(str.begin(), str.end(), str.begin(), std::toupper); See also: http://www.cplusplus.com/reference/locale/toupper/ This may also help in future: http://lmgtfy.com/?q=c%2B%2B+toupper -Riot On 30 June

Re: [Mingw-w64-public] IDE for MinGW64

2015-06-28 Thread Riot
I'd recommend code::blocks. On 28 Jun 2015 18:54, "Alexpux" wrote: > > 28 июня 2015 г., в 20:43, Developer 1 написал(а): > > Can anyone recommend me a IDE? > I use Win8.1 and I have been using VSExpress 2013, however, I have decided > to port to GCC due to it being closer to the standard. > >

Re: [Mingw-w64-public] finding the data file

2015-06-19 Thread Riot
In future can i recommend boost::filesystem to deal with your os-independent paths On 18 Jun 2015 22:45, "Hotmail (ArbolOne)" wrote: > I found the solution, the answer to my problem is > getenv("ARBOLONE") > > Thanks folks > > -Original Message- > From: Max S. > Sent: Thursday, June 18, 2

Re: [Mingw-w64-public] [AD] UltraGDB is released‏

2015-06-12 Thread Riot
Wot, no 32bit version? Shite! On 12 June 2015 at 02:56, Xu,Chiheng wrote: > Hi, Cygwin and MinGW guys, UltraGDB, a GDB GUI frontend on Windows > and Linux, is just released. > please try it out. > > http://www.ultragdb.com/ > > regards > > > This is an advertisement ! Sorry if this message

Re: [Mingw-w64-public] Multiple definition issue with -flto, MinGW-w64 4.9.1

2015-05-29 Thread Riot
s) and 300% more pre-linked objet size, and in return getting 42% smaller compiled code size and 6% performance improvement. In games, absolutely any measurable performance improvement is worth any amount of extra compile-time cost, but that may not be true for other fields. Regards, Riot On

Re: [Mingw-w64-public] Multiple definition issue with -flto, MinGW-w64 4.9.1

2015-05-29 Thread Riot
your libraries and any linked objects with the same gcc version and settings. It may also be worth it to try static linking. Riot On 29 May 2015 12:21, "Etienne Sandré-Chardonnal" wrote: > That's difficult to know, since the debugger seems to miss some > information. > The cu

Re: [Mingw-w64-public] I am in a in-path

2015-05-27 Thread Riot
Do you mean "I am at an impasse"? On 28 May 2015 00:29, "Hotmail (ArbolOne)" wrote: > I am in a in-path. I wrote a class that handles exceptions, > namespace abc{ > class Exception{...}; // This is my very large Exception class > } > > The way I'd like to use this class is by creating a smart

Re: [Mingw-w64-public] A logo for MinGW-w64

2015-04-12 Thread Riot
d bonus of generating more publicity for the project. Regards, Riot Hello, I have been unable to find any sort of existing logo for MinGW-w64. Please correct me if I am wrong. Though I've only been using "w64" for about a week, I already love it. I discovered this mailing list while at

Re: [Mingw-w64-public] Ohloh: I Use It

2014-07-07 Thread Riot
In what way does ohloh affect us, and why do we need to care if the mingw-w64 project is rated highly on it or not? On 7 July 2014 21:27, André Hentschel wrote: > Hi, > On Ohloh.net we have only 14 official users ([1]), while mingw has > nearly 300 and Wine more than 1000... > I think we should

Re: [Mingw-w64-public] LTO status?

2014-06-26 Thread Riot
I currently use LTO in production code. I and my team have been using LTO since gcc 4.7, although as you say it's more mature in 4.9. We are a small games development house so performance is critical and LTO makes a big difference to our release builds. However, I have also seen a few spurious b

Re: [Mingw-w64-public] [Poll] Move to git

2014-05-09 Thread Riot
[X] Yes, move to git [ ] No, continue with SVN On 9 May 2014 14:52, JonY wrote: > Hi all, > > You may also use the other thread for further discussion, please keep > this thread for votes only. > > For mingw-w64 developers, state your SF ID; for the registered voters, > simply reply with the sa

Re: [Mingw-w64-public] Register your vote (was Re: mingw-w64 may move to git in the future)

2014-05-02 Thread Riot
Hello, I'd like to register to vote. I'm quite new to the mingw-w64 project, but have been a mingw user for many years. I migrated in order to stay up to date with the latest versions of GCC and because the community is a great deal more accessable than that of the original mingw project. My ang

[Mingw-w64-public] intrin.h bug when using 3dnow, and patch

2014-04-20 Thread Riot
h i'm away from home so i can't find it right now, but it missed the 3dnow components. Patch: https://gist.github.com/slowriot/9903638 There may still be other parts of intrin.h that need #ifdef selected for other modes, too, but someone more experienced with the project will have to take