: normal
Priority: P3
Component: other
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: nightstrike at gmail dot com
GCC target triplet: x86_64-*-mingw32
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38294
--
nightstrike at gmail dot com changed:
What|Removed |Added
Severity|normal |enhancement
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38294
--- Comment #1 from nightstrike at gmail dot com 2008-11-27 17:43 ---
Created an attachment (id=16785)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16785&action=view)
My first crack at enabling the support
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38294
--- Comment #2 from nightstrike at gmail dot com 2008-12-08 07:48 ---
Created an attachment (id=16849)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16849&action=view)
Second attempt
This gets us further along
--
nightstrike at gmail dot com changed:
--- Comment #4 from nightstrike at gmail dot com 2008-12-13 21:19 ---
As per jakub, it is space separated.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38294
--- Comment #6 from nightstrike at gmail dot com 2008-12-13 21:59 ---
Created an attachment (id=16906)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16906&action=view)
Third attempt
There were a few lines in t-mingw32 that were commented out and shouldn't have
been t
--- Comment #7 from nightstrike at gmail dot com 2008-12-13 23:01 ---
Tested and verified on win64
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38294
--- Comment #8 from nightstrike at gmail dot com 2008-12-14 00:11 ---
To complete this patch, we need to make multilib not be the default.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38294
g
ReportedBy: nightstrike at gmail dot com
GCC target triplet: *-w64-mingw*
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40376
--- Comment #1 from nightstrike at gmail dot com 2009-06-25 13:58 ---
I imagine this applies to any target, not just win64 targets. I can't change
that setting, though.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40516
mingw32
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: major
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: nightstrike at gmail dot com
GCC build triplet:
: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: nightstrike at gmail dot com
GCC target triplet: x86_64-pc-mingw32
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33652
--
nightstrike at gmail dot com changed:
What|Removed |Added
Severity|critical|blocker
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33652
--- Comment #1 from nightstrike at gmail dot com 2007-10-10 18:44 ---
Changed the title to better reflect what was transpiring.
This problem has since been fixed, so I am closing it.
--
nightstrike at gmail dot com changed:
What|Removed |Added
: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: other
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: nightstrike at gmail dot com
GCC target triplet: x86_64-pc-mingw32
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33797
--- Comment #8 from nightstrike at gmail dot com 2007-10-20 19:12 ---
Explicit paths for mingw for as and ld should not be required. We fixed this
for mingw-w64, and the same thing should be applied to mingw32. This same
error occurs regardless of whether or not you are in a mingw
Product: gcc
Version: tree-ssa
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: nightstrike at gmail dot com
GCC build triplet: i686-pc-cygwin
--- Comment #1 from nightstrike at gmail dot com 2008-08-12 04:46 ---
Created an attachment (id=16057)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16057&action=view)
Preprocessed source
This is the preprocessed source for the file that causes the ICE
--
http://gcc.
--- Comment #2 from nightstrike at gmail dot com 2008-08-12 04:46 ---
Preprocessed source added as attachment. Also note that the bootstrap gcc was
built with cygwin's gcc, which is a modified 3.4.4.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37091
--- Comment #6 from nightstrike at gmail dot com 2008-08-13 14:23 ---
Is 2.95 still the minimum gcc required for the build?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37086
--- Comment #8 from nightstrike at gmail dot com 2008-08-22 06:47 ---
I can confirm this bug (seeing as how the one I wrote got duped to here). Can
someone update the status to confirmed?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37086
--- Comment #10 from nightstrike at gmail dot com 2008-08-22 17:41 ---
How can you close this if the tuples merge makes it impossible to build gcc
with version 3.4? The minimum gcc is still 2.95.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37086
--- Comment #14 from nightstrike at gmail dot com 2008-09-12 05:47 ---
I just wanted to confirm that Joesph's patch does indeed work (thank you!), and
ask that the status of this PR change from INVALID to FIXED.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37086
nu dot org
ReportedBy: nightstrike at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37503
--- Comment #2 from nightstrike at gmail dot com 2008-09-12 20:32 ---
Re-opening, valid PR as per 30484. Will close as duplicate.
--
nightstrike at gmail dot com changed:
What|Removed |Added
--- Comment #3 from nightstrike at gmail dot com 2008-09-12 20:32 ---
Marking as duplicate of 30484.
*** This bug has been marked as a duplicate of 30484 ***
--
nightstrike at gmail dot com changed:
What|Removed |Added
--- Comment #7 from nightstrike at gmail dot com 2008-09-12 20:32 ---
*** Bug 37503 has been marked as a duplicate of this bug. ***
--
nightstrike at gmail dot com changed:
What|Removed |Added
--- Comment #23 from nightstrike at gmail dot com 2008-09-21 17:06 ---
(In reply to comment #22)
> I'm probably not the one who'll find the core of the bug but I'd like to
> mention two simple facts:
Thanks for your feedback!
> 1: mingw-w64-bin_i686-mingw_200
portedBy: nightstrike at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37641
--- Comment #6 from nightstrike at gmail dot com 2008-09-25 05:00 ---
What is the output of g++ -v?
Are you using the win32 cross compiler, or the win64 native compiler?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37121
--- Comment #3 from nightstrike at gmail dot com 2008-09-25 15:04 ---
I think that was a mistake. He was just trying to confirm the PR, and probably
meant to set it to WAITING as opposed to ASSIGNED. I saw your emails to
gcc-patches. If you could commit the change, that'd be aw
Severity: normal
Priority: P3
Component: other
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: nightstrike at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35151
--- Comment #1 from nightstrike at gmail dot com 2008-02-12 02:39 ---
http://gcc.gnu.org/ml/gcc-patches/2008-02/msg00350.html
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35124
t gcc dot gnu dot org
ReportedBy: nightstrike at gmail dot com
GCC host triplet: x86_64-pc-mingw32
GCC target triplet: x86_64-pc-mingw32
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35159
--
nightstrike at gmail dot com changed:
What|Removed |Added
Severity|normal |blocker
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35159
--- Comment #2 from nightstrike at gmail dot com 2008-02-14 01:17 ---
This bug needs to be finished off before 4.3.0 closes...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35124
--- Comment #3 from nightstrike at gmail dot com 2008-02-14 01:53 ---
Can we have this fixed before 4.3.0? x86_64-pc-mingw32 is a new target for
this release, and it shouldn't be delivered completely broken.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35159
--- Comment #12 from nightstrike at gmail dot com 2008-02-14 14:27 ---
Subject: Re: g++ inoperable with no error message
On 14 Feb 2008 08:15:35 -, jakub at gcc dot gnu dot org
<[EMAIL PROTECTED]> wrote:
>
>
> --- Comment #5 from jakub at gcc dot gnu dot org 2
--- Comment #13 from nightstrike at gmail dot com 2008-02-14 14:29 ---
Addendum - this applies to gfortran, as well.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35159
--- Comment #14 from nightstrike at gmail dot com 2008-02-16 17:22 ---
edited title to reflect gfortran failure, as well.
--
nightstrike at gmail dot com changed:
What|Removed |Added
--- Comment #1 from nightstrike at gmail dot com 2008-02-19 05:32 ---
Here is the email thread that started it all:
http://gcc.gnu.org/ml/gcc-help/2008-02/msg00197.html
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35250
t_modules= { module= gnuserv; };
host_modules= { module= gprof; };
host_modules= { module= gzip; };
--
Summary: gmp and mpfr are erroneously configured with --target
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: trivial
Priority: P3
Component: other
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: nightstrike at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35250
--- Comment #9 from nightstrike at gmail dot com 2008-02-19 22:23 ---
Was this patch ever submitted?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34571
Severity: normal
Priority: P3
Component: web
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: nightstrike at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35256
--- Comment #2 from nightstrike at gmail dot com 2008-02-23 11:12 ---
Here's an even better way to do it:
Index: configure.ac
===
--- configure.ac(revision 132554)
+++ configure.ac(working
--- Comment #2 from nightstrike at gmail dot com 2008-02-24 03:31 ---
This is a very simple fix. Can someone add it?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35250
--- Comment #16 from nightstrike at gmail dot com 2008-03-06 03:00 ---
Created an attachment (id=15267)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15267&action=view)
Preprocssed source for the testcase mentioned
I took the code that I mentioned in the first post in t
--- Comment #18 from nightstrike at gmail dot com 2008-03-06 05:09 ---
(In reply to comment #17)
> What is the Fortran test case that makes this is a gfortran issue?
PROGRAM HelloWorld
WRITE(*,*) "Hello World!"
END PROGRAM
I haven't tested that again with
--- Comment #19 from nightstrike at gmail dot com 2008-03-06 16:08 ---
Ok, compiling the aforementioned "Hello, world!" program using "gfortran
--save-temps hello.f90" results in f951.exe maxing out the CPU forever.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35159
--- Comment #1 from nightstrike at gmail dot com 2008-04-06 14:55 ---
Created an attachment (id=15434)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15434&action=view)
Preprocessed source
This is the preprocessed source that causes the ICE.
--
http://gcc.gnu.org/b
Component: tree-optimization
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: nightstrike at gmail dot com
GCC host triplet: i686-pc-linux
GCC target triplet: x86_64-pc-mingw32
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35842
--- Comment #2 from nightstrike at gmail dot com 2008-04-06 15:07 ---
To clarify the title, the ICE goes away with all optimization levels when
-fno-tree-ch is used.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35842
--- Comment #18 from nightstrike at gmail dot com 2008-04-06 16:03 ---
What is the status on this? I am having a lot of test timeouts when testing
the x86_64-pc-mingw cross compiler, as sometimes there are slow programd and
annoying ssh network delays. Extending the timeout in a
--- Comment #11 from nightstrike at gmail dot com 2009-02-06 04:21 ---
Created an attachment (id=17259)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17259&action=view)
Kai's attempt
This patch has a few caveats:
You can't use the winsup link hack to work arou
--- Comment #9 from nightstrike at gmail dot com 2009-02-14 22:56 ---
Verified to fail on win32 and win64, not just win64. Can someone with
sufficient privileges adjust "Target"?
Verified to work in 4.3, so this is a regression.
--
http://gcc.gnu.org/bugzilla/show_
--- Comment #12 from nightstrike at gmail dot com 2009-03-09 02:10 ---
Was this broken in 4.3 compilers? Is it a 4.4 regression?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37121
--- Comment #2 from nightstrike at gmail dot com 2009-03-14 15:46 ---
http://gcc.gnu.org/ml/gcc-patches/2009-03/msg00638.html
--
nightstrike at gmail dot com changed:
What|Removed |Added
--- Comment #2 from nightstrike at gmail dot com 2009-03-14 15:49 ---
http://gcc.gnu.org/ml/gcc-patches/2009-03/msg00636.html
--
nightstrike at gmail dot com changed:
What|Removed |Added
--- Comment #3 from nightstrike at gmail dot com 2009-03-14 15:52 ---
http://gcc.gnu.org/ml/gcc-patches/2009-03/msg00634.html
--
nightstrike at gmail dot com changed:
What|Removed |Added
--- Comment #2 from nightstrike at gmail dot com 2009-03-14 15:54 ---
http://gcc.gnu.org/ml/gcc-patches/2009-03/msg00641.html
--
nightstrike at gmail dot com changed:
What|Removed |Added
--- Comment #5 from nightstrike at gmail dot com 2009-03-14 15:57 ---
http://gcc.gnu.org/ml/gcc-patches/2009-03/msg00640.html
--
nightstrike at gmail dot com changed:
What|Removed |Added
--- Comment #2 from nightstrike at gmail dot com 2009-03-14 16:00 ---
http://gcc.gnu.org/ml/gcc-patches/2009-03/msg00639.html
--
nightstrike at gmail dot com changed:
What|Removed |Added
--- Comment #11 from nightstrike at gmail dot com 2009-03-20 05:28 ---
I can confirm that our 4.3 release worked, and that this is a 4.4 regression.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39356
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49111
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46501
nightstrike changed:
What|Removed |Added
See Also||http://gcc.gnu.org/bugzilla
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56412
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56412
--- Comment #5 from nightstrike 2013-04-19
17:46:37 UTC ---
CYGPATH_W gets set correctly, but libtool seems to ignore it.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56909
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot
--- Comment #12 from nightstrike at gmail dot com 2009-09-12 05:36 ---
Current warning list as of revision 151630:
../../../../../build/gcc/gcc/libgfortran/io/write.c:328:8: warning: passing
argument 2 of 'write_default_char4' from incompatible pointer type
../../../../../bui
--- Comment #15 from nightstrike at gmail dot com 2009-09-21 16:30 ---
Current list:
../../../../../build/gcc/gcc/libgfortran/io/list_read.c:1847:10: warning:
variable 'elem' might be clobbered by 'longjmp' or 'vfork'
../../../../../build/gcc/gcc/libg
--- Comment #16 from nightstrike at gmail dot com 2009-09-21 16:33 ---
(In reply to comment #14)
> Subject: Bug 41219
>
> Author: jvdelisle
> Date: Sat Sep 12 15:08:27 2009
> New Revision: 151653
As of r151914, this warning still exists when the host=linux64 and t
--- Comment #18 from nightstrike at gmail dot com 2009-09-21 17:36 ---
(In reply to comment #17)
> > ../../../../../build/gcc/gcc/libgfortran/intrinsics/iso_c_binding.c:98:24:
> > warning: 'str' may be used uninitialized in this function
>
> I
--- Comment #20 from nightstrike at gmail dot com 2009-09-21 18:12 ---
(In reply to comment #19)
> (In reply to comment #18)
> > (In reply to comment #17)
> > > > ../../../../../build/gcc/gcc/libgfortran/intrinsics/iso_c_binding.c:98:24:
> > > > warning
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42607
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54080
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36819
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43682
--- Comment #3 from nightstrike 2011-10-03
13:06:38 UTC ---
Who can update the in-tree boehm-gc?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42304
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47485
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42954
--- Comment #18 from nightstrike 2011-10-27
02:00:37 UTC ---
We have a patch. What else is missing?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52672
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50048
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42954
--- Comment #20 from nightstrike 2012-06-22
02:05:45 UTC ---
As we're in 4.8 now, consider this a friendly ping :)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28145
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50461
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot
riable ret never used
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: trivial
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: nightstrike at gmail dot com
GCC build tripl
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: nightstrike at gmail dot com
Target Milestone: ---
I see these warnings building gfortran across many versions including current
trunk:
../../gcc/fortran/gfortra
onent: libfortran
Assignee: unassigned at gcc dot gnu.org
Reporter: nightstrike at gmail dot com
Target Milestone: ---
Host: x86_64-pc-linux-gnu
Target: x86_64-pc-linux-gnu
Build: x86_64-pc-linux-gnu
Compiling a basic fortran hello world y
Component: libfortran
Assignee: unassigned at gcc dot gnu.org
Reporter: nightstrike at gmail dot com
Target Milestone: ---
While building libgfortran, I receive the following warnings for
-Wmisleading-indentation:
../../../libgfortran/generated/minloc0_4_i1.c: In function
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: nightstrike at gmail dot com
Target Milestone: ---
#include
struct Input {
std::vector>;
};
$ g++ xxx.cc
xxx.cc:4:7: error: a template-id may not appear in a us
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86095
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82711
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: nightstrike at gmail dot com
Target Milestone: ---
$ cat a.cc
int const f() { return 0; }
int * const g() { return 0; }
$ g++ a.cc -c -Wignored-qualifiers
a.cc:1:5: warning: type
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606
--- Comment #11 from nightstrike ---
This now works with gcc 8. I haven't tried other versions.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606
--- Comment #12 from nightstrike ---
(In reply to Martin Sebor from comment #9)
> A similar test case not involving arrays:
>
> $ cat z.c && /build/gcc-trunk-svn/gcc/xgcc -B /build/gcc-trunk-svn/gcc -S
> -Wall -Wextra -o/dev/null -xc++ z.c
> typ
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82711
--- Comment #6 from nightstrike ---
(In reply to Martin Sebor from comment #5)
> -Wignored-qualifiers has been in -Wextra since r131499. Based on the
> Firefox review I think the request is actually to remove the warning from
> -Wextra (or they
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54080
--- Comment #4 from nightstrike ---
This still crashes with gcc 8.1.1 20180531
++
Assignee: unassigned at gcc dot gnu.org
Reporter: nightstrike at gmail dot com
Target Milestone: ---
This works:
#include
bool f() {
std::random_device r;
std::mt19937 gen(r());
std::bernoulli_distribution d(0.5);
return d(gen);
}
This easy
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: nightstrike at gmail dot com
Target Milestone: ---
ICC 18 is able to vectorize this loop, while GCC 8 is not.
#include
std::size_t f(std::vector> const & v) {
std::size_t ret = 0;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69224
--- Comment #11 from nightstrike ---
Will this be back ported to 6 and 7?
1 - 100 of 336 matches
Mail list logo
