Send MinGW-Notify mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.osdn.me/mailman/listinfo/mingw-notify
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of MinGW-Notify digest..."


Please do not reply to this notification; the sender address is unable to 
accept incoming e-mail.  If you wish to unsubscribe you can do so at 
https://lists.osdn.me/mailman/listinfo/mingw-notify.



Today's Topics:

   1. [mingw] #41753: -O2 Bug Infinite Loop (MinGW Notification List)
   2. [mingw] #41753: -O2 Bug Infinite Loop (MinGW Notification List)


----------------------------------------------------------------------

Message: 1
Date: Sat, 13 Mar 2021 04:07:18 +0900
From: MinGW Notification List <[email protected]>
To: OSDN Ticket System <[email protected]>
Subject: [MinGW-Notify] [mingw] #41753: -O2 Bug Infinite Loop
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8

#41753: -O2 Bug Infinite Loop

  Open Date: 2021-03-13 04:07
Last Update: 2021-03-13 04:07

URL for this Ticket:
    https://osdn.net//projects/mingw/ticket/41753
RSS feed for this Ticket:
    https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=41753

---------------------------------------------------------------------

Last Changes/Comment on this Ticket:
2021-03-13 04:07 Updated by: first_last
 * New Ticket "-O2 Bug Infinite Loop" created


---------------------------------------------------------------------
Ticket Status:

      Reporter: first_last
         Owner: (None)
          Type: Issues
        Status: Open
      Priority: 9 - Highest
     MileStone: Create a 64bit build environment for the MinGW.org project.
     Component: GCC
      Severity: 9 - Highest
    Resolution: None
---------------------------------------------------------------------

Ticket details:

This Piece of Code is getting Stuck In Infinite Loop when Using -O2 Flag  
#include <bits/stdc++.h>
using namespace std;
typedef long long int ll;

ll f() {

  for (int i = 0; i < 3; i++) {
    for (int j = 0; j < 2; j++) {
     cout << i << " " << j << endl;
    }
  }
}

int main() {
  f();

  return 0;
}


-- 
Ticket information of MinGW - Minimalist GNU for Windows project
MinGW - Minimalist GNU for Windows Project is hosted on OSDN

Project URL: https://osdn.net/projects/mingw/
OSDN: https://osdn.net

URL for this Ticket:
    https://osdn.net/projects/mingw/ticket/41753
RSS feed for this Ticket:
    https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=41753


------------------------------

Message: 2
Date: Fri, 12 Mar 2021 22:32:58 +0000
From: MinGW Notification List <[email protected]>
To: OSDN Ticket System <[email protected]>
Subject: [MinGW-Notify] [mingw] #41753: -O2 Bug Infinite Loop
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8

#41753: -O2 Bug Infinite Loop

  Open Date: 2021-03-12 19:07
Last Update: 2021-03-12 22:32

URL for this Ticket:
    https://osdn.net//projects/mingw/ticket/41753
RSS feed for this Ticket:
    https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=41753

---------------------------------------------------------------------

Last Changes/Comment on this Ticket:
2021-03-12 22:32 Updated by: keith
 * Status Update from Open to Closed
 * Resolution Update from None to Rejected
 * Milestone Update from Create a 64bit build environment for the MinGW.org 
project. to (None)
 * Severity Update from 9 - Highest to 1 - Lowest
 * Priority Update from 9 - Highest to 1 - Lowest
 * Details Updated

Comment:

Several comments:
What part of the instruction: "priority is to be assigned only by an approved 
MinGW developer" do you not understand?  You are not such a developer.  Thus 
your attempt to escalate priority guarantees that this ticket will be treated 
as lowest priority.
This is not specifically a MinGW bug.  Yes, I can see that it misbehaves as you 
suggest, but it exhibits similar misbehaviour when I compile it as a native 
GNU/Linux application, (using GCC-10.2 on Manjaro Linux).  If you want it 
pursued, you need to raise the issue on the GCC bug tracker.
You really should not use #include <bits/stdc++.h> directly in user code; 
that's an internal-use header.  In this example, you should be using #include 
<iostream>.
If I compile your code, I see a warning about a missing return statement, in 
your non-void f() function.  Address that warning, either by adding the missing 
return statement, or by declaring void f(), and the misbehaviour does not occur.
Given the above, I am not going to pursue this.

---------------------------------------------------------------------
Ticket Status:

      Reporter: first_last
         Owner: (None)
          Type: Issues
        Status: Closed
      Priority: 1 - Lowest
     MileStone: (None)
     Component: GCC
      Severity: 1 - Lowest
    Resolution: Rejected
---------------------------------------------------------------------

Ticket details:

This Piece of Code is getting Stuck In Infinite Loop when Using -O2 Flag  
 #include <bits/stdc++.h> using namespace std; typedef long long int ll;  ll 
f() {    for (int i = 0; i < 3; i++) {     for (int j = 0; j < 2; j++) {      
cout << i << " " << j << endl;     }   } }  int main() {   f();    return 0; }

-- 
Ticket information of MinGW - Minimalist GNU for Windows project
MinGW - Minimalist GNU for Windows Project is hosted on OSDN

Project URL: https://osdn.net/projects/mingw/
OSDN: https://osdn.net

URL for this Ticket:
    https://osdn.net/projects/mingw/ticket/41753
RSS feed for this Ticket:
    https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=41753


------------------------------

Subject: Digest Footer

_______________________________________________
MinGW-Notify mailing list
[email protected]
https://lists.osdn.me/mailman/listinfo/mingw-notify


------------------------------

End of MinGW-Notify Digest, Vol 42, Issue 4
*******************************************

Reply via email to