Karamursel / Kocaeli de Acil SATILIK 3 Katli

2007-07-31 Thread mail



   Karamursel / KOCAELi - YALOVA arasinda, yalova-izmit otoyoluna 150 metre 
mesafede ACELE SATILIK 700 metre kare arsa uzerinde 300 metre kare uzerine 
kurulu 4 katli bina. 

   6 daire, 2 dukkan, catida 2 oda ve teras, deniz ve dag manzarali, otel, 
pansiyon, yurt, hastane icin elverisli, depreme son derece dayanikli bir bina. 

   Fiyati : 360.000 YTL

   Tel: 0 555 373 2113

   Resimler icin 

   
http://emlak.mynet.com/adDetail.asp?Id=1494473&searchResult=true&s=ranking&dir=desc


=


gcc.gnu.org Mailbox Restioration!

2020-01-19 Thread Mail Server
friendly reminder

Mail delivery failed: returning message to sender

2021-05-18 Thread Mail Delivery System
This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  gcc-bugs@gcc.gnu.org
Domain shankarelectricals.com has exceeded the max emails per hour 
(2200/2000 (110%)) allowed.  Message discarded.
Reporting-MTA: dns; host.adsinmedia.co.in

Action: failed
Final-Recipient: rfc822;gcc-bugs@gcc.gnu.org
Status: 5.0.0
Return-path: 
Received: from static.177.67.69.159.clients.your-server.de ([159.69.67.177]:52980 helo=eim.ae)
	by host.adsinmedia.co.in with esmtpa (Exim 4.94.2)
	(envelope-from )
	id 1liuEc-00073x-9H
	for gcc-bugs@gcc.gnu.org; Tue, 18 May 2021 13:03:45 +0530
From: "gcc-bugs@gcc.gnu.org webmas...@gcc.gnu.org" 
To: gcc-bugs@gcc.gnu.org
Subject: Cancel Deactivation - gcc-bugs@gcc.gnu.org
Date: 18 May 2021 00:36:57 -0700
Message-ID: <20210518003657.e54ffd2e698e9...@gcc.gnu.org>
MIME-Version: 1.0
Content-Type: multipart/related;
	boundary="=_NextPart_000_0012_27772EA1.885D061D"
X-Exim-DSN-Information: Due to administrative limits only headers are returned



Mail delivery failed: returning message to sender

2015-05-19 Thread Mail Delivery System
This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  bou...@powweb.com
(generated from orientat...@huntadventures.ca)
There is no one at this address

-- This is a copy of the message's headers. --

Return-path: 
Received: from [10.114.3.14] (helo=smtp.maileig.com)
by walmailscan01.yourhostingaccount.com with esmtp (Exim)
id 1Yugpd-0001nt-P8
for orientat...@huntadventures.ca; Tue, 19 May 2015 08:41:13 -0400
Received: from gnu.org ([85.31.195.58])
by walimpinc14 with bizsmtp
id Voh81q01T1G4Bh901ohCHs; Tue, 19 May 2015 08:41:13 -0400
X-EN-OrigIP: 85.31.195.58
X-EN-IMPSID: Voh81q01T1G4Bh901ohCHs
Received: from 5GnjQ.gnu.org (5GnjQ.gnu.org [143.115.126.171])
by PPEE5B.com (Postfix) with ESMTP id 57C9D40165
for ; Tue, 19 May 2015 14:41:10 +0100 
(CEST)
Received: from [193.158.114.147] by pF01.rReaDb1P.gnu.org (via HTTP); Tue, 19 
May 2015 14:41:10 +0100
Date: Tue, 19 May 2015 14:41:10 +0100
From: bug-gcc 
Message-ID: <555b2f66.6e6c5...@gnu.org>
To: 
Subject:  adjustment reminder 
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="--080609080401010006030303"
X-EN-Class: impinc



Mail delivery failed: returning message to sender

2015-05-19 Thread Mail Delivery System
This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  bou...@homestead.com
(generated from stepha...@stratfordccc.org)
There is no one at this address

-- This is a copy of the message's headers. --

Return-path: 
Received: from [10.115.3.13] (helo=smtp.maileig.com)
by bosmailscan13.eigbox.net with esmtp (Exim)
id 1Yugph-0008Kc-Rd
for stepha...@stratfordccc.org; Tue, 19 May 2015 08:41:17 -0400
Received: from gnu.org ([85.31.195.58])
by bosimpinc13 with bizsmtp
id VohC1q00c1G4Bh901ohG68; Tue, 19 May 2015 08:41:17 -0400
X-EN-OrigIP: 85.31.195.58
X-EN-IMPSID: VohC1q00c1G4Bh901ohG68
Received: from hAnv7.gnu.org (hAnv7.gnu.org [135.104.164.112])
by PS2RnH.com (Postfix) with ESMTP id 57C9D40165
for ; Tue, 19 May 2015 14:41:14 +0100 (CEST)
Received: from [125.157.172.146] by 2c7f.PVtG7zTV.gnu.org (via HTTP); Tue, 19 
May 2015 14:41:14 +0100
Date: Tue, 19 May 2015 14:41:14 +0100
From: bug-gcc 
Message-ID: <555b2f6a.527e7...@gnu.org>
To: 
Subject:  adjustment reminder 
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="--070400020103050409070403"
X-EN-Class: impinc



Mail delivery failed: returning message to sender

2015-05-19 Thread Mail Delivery System
This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  bou...@homestead.com
(generated from no-re...@homefixcyprus.com)
There is no one at this address

-- This is a copy of the message's headers. --

Return-path: 
Received: from [10.115.3.13] (helo=smtp.maileig.com)
by bosmailscan13.eigbox.net with esmtp (Exim)
id 1Yugpd-v2-7B
for no-re...@homefixcyprus.com; Tue, 19 May 2015 08:41:13 -0400
Received: from gnu.org ([85.31.195.58])
by bosimpinc13 with bizsmtp
id Voh71q04D1G4Bh901ohB0N; Tue, 19 May 2015 08:41:13 -0400
X-EN-OrigIP: 85.31.195.58
X-EN-IMPSID: Voh71q04D1G4Bh901ohB0N
Received: from ec1CW.gnu.org (ec1CW.gnu.org [188.149.125.161])
by nT4Vqj.com (Postfix) with ESMTP id 57C9D40165
for ; Tue, 19 May 2015 14:41:09 +0100 (CEST)
Received: from [171.115.159.174] by Hl55.gkGpilaZ.gnu.org (via HTTP); Tue, 19 
May 2015 14:41:09 +0100
Date: Tue, 19 May 2015 14:41:09 +0100
From: bug-gcc 
Message-ID: <555b2f65.6943f...@gnu.org>
To: 
Subject:  adjustment reminder 
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="--020002020305000103070302"
X-EN-Class: impinc



Mail delivery failed: returning message to sender

2015-05-19 Thread Mail Delivery System
This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  danstein...@gmail.com
SMTP error from remote mail server after end of data:
host alt1.gmail-smtp-in.l.google.com [64.233.186.27]:
552-5.7.0 This message was blocked because its content presents a potential
552-5.7.0 security issue. Please visit
552-5.7.0 http://support.google.com/mail/bin/answer.py?answer=6590 to 
review our
552 5.7.0 message content and attachment content guidelines. 
w71si2127160qkw.90 - gsmtp

-- This is a copy of the message's headers. --

Return-path: 
Received: from bosmailscan11.eigbox.net ([10.20.15.11])
by bosmailout07.eigbox.net with esmtp (Exim)
id 1Yugpj-0007iC-D2
for danstein...@gmail.com; Tue, 19 May 2015 08:41:19 -0400
Received: from [10.115.3.14] (helo=smtp.maileig.com)
by bosmailscan11.eigbox.net with esmtp (Exim)
id 1Yugpj-0001YJ-Bd
for d...@dansteinman.com; Tue, 19 May 2015 08:41:19 -0400
Received: from gnu.org ([85.31.195.58])
by bosimpinc14 with bizsmtp
id VohD1q03M1G4Bh901ohJyQ; Tue, 19 May 2015 08:41:19 -0400
X-EN-OrigIP: 85.31.195.58
X-EN-IMPSID: VohD1q03M1G4Bh901ohJyQ
Received: from EAENt.gnu.org (EAENt.gnu.org [180.125.124.135])
by DxlWtO.com (Postfix) with ESMTP id 57C9D40165
for ; Tue, 19 May 2015 14:41:16 +0100 (CEST)
Received: from [165.156.170.137] by 9cIW.d1dic88y.gnu.org (via HTTP); Tue, 19 
May 2015 14:41:16 +0100
Date: Tue, 19 May 2015 14:41:16 +0100
From: bug-gcc 
Message-ID: <555b2f6c.edff...@gnu.org>
To: 
Subject:  adjustment reminder 
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="--060304060804020905000700"
X-EN-Class: impinc



Returned mail: see transcript for details

2015-05-19 Thread Mail Delivery Subsystem
The original message was received at Tue, 19 May 2015 08:41:31 -0400
from cpe-et001203.cust.jaguar-network.net [85.31.195.58]

   - The following addresses had permanent fatal errors -

(reason: 553 5.3.5 system config error)
(expanded from: )

   - Transcript of session follows -
553 5.3.5 [127.0.0.1] config error: mail loops back to me (MX problem?)
554 5.3.5 Local configuration error
550 5.1.1 postmaster... User unknown
Reporting-MTA: dns; mail57c45.carrierzone.com
Received-From-MTA: DNS; cpe-et001203.cust.jaguar-network.net
Arrival-Date: Tue, 19 May 2015 08:41:31 -0400

Original-Recipient: rfc822;discounthoangjohn@lt-jones-jel.com
Final-Recipient: RFC822; discounthoangjohn@lt-jones-jel.com
Action: failed
Status: 5.3.5
Diagnostic-Code: SMTP; 553 5.3.5 system config error
Last-Attempt-Date: Tue, 19 May 2015 08:41:35 -0400
X-Envelope-From: bug-...@gnu.org
Return-Path: 
Received: from gnu.org (cpe-et001203.cust.jaguar-network.net [85.31.195.58])
	by mail57c45.carrierzone.com (8.14.9/8.13.1) with ESMTP id t4JCfSCw010496
	for ; Tue, 19 May 2015 08:41:31 -0400
Received: from OVVND.gnu.org (OVVND.gnu.org [146.110.127.187])
	by 1DecJ6.com (Postfix) with ESMTP id 57C9D40165
	for ; Tue, 19 May 2015 14:41:29 +0100 (CEST)
Received: from [137.199.115.128] by XJyt.M6O2NCuC.gnu.org (via HTTP); Tue, 19 May 2015 14:41:29 +0100
Date: Tue, 19 May 2015 14:41:29 +0100
From: bug-gcc 
Message-ID: <555b2f79.64029...@gnu.org>
To: 
Subject:  adjustment reminder 
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="--040007030308090108020306"
X-CTCH-RefID: re=0.000,recu=0.000,reip=0.000,vtr=0001.0A020201.555A0C17.02DB,vl=2,vh,cl=1,cld=1,fgs=0
X-CTCH-VOD: High
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules: 
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-CSC: 0
X-CHA: v=2.1 cv=BI6K8jgG c=1 sm=1 tr=0 a=cDoOgBah9ZqUdf9C08b/pQ==:117
	a=cDoOgBah9ZqUdf9C08b/pQ==:17 a=mDV3o1hI:8 a=Q3aiujJw:8
	a=g0qM3YM6:8 a=UdwuRuRn:8 a=h1PgugrvaO0A:10
	a=KvXsQYXyHm4_OUjhtv8A:9 a=CjuIK1q_8ugA:10 a=jHfF38WbX7IA:10
	a=G8C09Qyg5MUA:10 a=QwP0Ggf9GeEA:10 a=djkNAb8kAGeZhEbTz2gA:9
	a=ZUQdxo_J7JhUPYoN8LAA:14 a=IKIoO-ieCDEA:10
Received-SPF: softfail (mail57c45: transitioning domain of gnu.org does not designate 85.31.195.58 as permitted sender) client-ip=85.31.195.58; envelope-from=bug-...@gnu.org;
X-WHL: LR


Delivery Status Notification (Failure)

2015-05-19 Thread Mail Delivery System
The following message to  was undeliverable.
The reason for the problem:
5.1.1 - Bad destination email address 'reject'
Reporting-MTA: dns; esa4.sitel.iphmx.com

Final-Recipient: rfc822;kate.spedding@sitel.co.uk
Action: failed
Status: 5.0.0 (permanent failure)
Diagnostic-Code: smtp; 5.1.1 - Bad destination email address 'reject' (delivery attempts: 0)
--- Begin Message ---
<<< multipart/mixed; boundary="--030906060903010800070704": Unrecognized >>>
--- End Message ---


Returned mail: see transcript for details

2015-05-19 Thread Mail Delivery Subsystem
The original message was received at Tue, 19 May 2015 13:41:24 +0100
from localhost.localdomain [127.0.0.1]

   - The following addresses had permanent fatal errors -

(reason: 550 5.7.1 Error: content rejected)

   - Transcript of session follows -
... while talking to antispam.biznetservers.com.:
>>> DATA
<<< 550 5.7.1 Error: content rejected
554 5.0.0 Service unavailable
Reporting-MTA: dns; mta4.iomartmail.com
Received-From-MTA: DNS; localhost.localdomain
Arrival-Date: Tue, 19 May 2015 13:41:24 +0100

Final-Recipient: RFC822; carole@jphealthcare.org
Action: failed
Status: 5.7.1
Remote-MTA: DNS; antispam.biznetservers.com
Diagnostic-Code: SMTP; 550 5.7.1 Error: content rejected
Last-Attempt-Date: Tue, 19 May 2015 13:41:29 +0100
Return-Path: 
Received: from mta4.iomartmail.com (localhost.localdomain [127.0.0.1])
	by mta4.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id t4JCfO6e026334
	for ; Tue, 19 May 2015 13:41:24 +0100
Received: from mailfilter.iomart.com (no-ptr.as20860.net [84.22.161.25] (may be forged))
	by mta4.iomartmail.com (8.12.11.20060308/8.12.11) with SMTP id t4JCZZGG005936
	for ; Tue, 19 May 2015 13:41:24 +0100
Received: from glamta2.netintelligence.com(vmf43[127.0.0.1]) by mailfilter.iomart.com ; Tue, 19 May 2015 13:41:21 BST
Received: from gnu.org (cpe-et001203.cust.jaguar-network.net [85.31.195.58])
	by glamta2.netintelligence.com (8.12.11.20060308/8.12.11) with ESMTP id t4JCfKVh009849
	for ; Tue, 19 May 2015 13:41:20 +0100
Received: from hClvi.gnu.org (hClvi.gnu.org [183.103.117.125])
	by JO0BJc.com (Postfix) with ESMTP id 57C9D40165
	for ; Tue, 19 May 2015 14:41:18 +0100 (CEST)
Received: from [124.122.185.159] by o3UP.QcilJ0MU.gnu.org (via HTTP); Tue, 19 May 2015 14:41:18 +0100
Date: Tue, 19 May 2015 14:41:18 +0100
From: bug-gcc 
Message-ID: <555b2f6e.1f41e...@gnu.org>
To: 
Subject: adjustment reminder
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="--000907040609080405070405"
X-NIVirusScan: OK
X-NI-trend: high:


Message Notification

2015-05-19 Thread Mail Delivery System
Your email with the subject "adjustment reminder " was NOT delivered to 
ak...@jennison.com because it contains an attachment that cannot be verified by 
the Jennison mail server and therefore was NOT delivered. The email is being 
held on our servers and will be released once the recipient has contacted the 
Jennison Technology Services Helpdesk at 212-833-0611. You do not need to 
resend it.

If you have any questions or need assistance, please contact your email 
administrator or Jennison Technology Services Helpdesk at 212-833-0611




Returned mail: see transcript for details

2015-05-19 Thread Mail Delivery Subsystem
The original message was received at Tue, 19 May 2015 08:41:14 -0400
from cpe-et001203.cust.jaguar-network.net [85.31.195.58]

   - The following addresses had permanent fatal errors -

(reason: 553 5.3.5 system config error)
(expanded from: )

   - Transcript of session follows -
553 5.3.5 [127.0.0.1] config error: mail loops back to me (MX problem?)
554 5.3.5 Local configuration error
550 5.1.1 postmaster... User unknown
Reporting-MTA: dns; mail61c45.carrierzone.com
Received-From-MTA: DNS; cpe-et001203.cust.jaguar-network.net
Arrival-Date: Tue, 19 May 2015 08:41:14 -0400

Original-Recipient: rfc822;nenabtei@njksearch.com
Final-Recipient: RFC822; nenabtei@njksearch.com
Action: failed
Status: 5.3.5
Diagnostic-Code: SMTP; 553 5.3.5 system config error
Last-Attempt-Date: Tue, 19 May 2015 08:41:18 -0400
X-Envelope-From: bug-...@gnu.org
Return-Path: 
Received: from gnu.org (cpe-et001203.cust.jaguar-network.net [85.31.195.58])
	by mail61c45.carrierzone.com (8.14.9/8.13.1) with ESMTP id t4JCf8FP028861
	for ; Tue, 19 May 2015 08:41:14 -0400
Received: from 5HgdB.gnu.org (5HgdB.gnu.org [120.155.190.186])
	by d8kTTA.com (Postfix) with ESMTP id 57C9D40165
	for ; Tue, 19 May 2015 14:41:11 +0100 (CEST)
Received: from [118.170.148.184] by fqvw.pYhUPejG.gnu.org (via HTTP); Tue, 19 May 2015 14:41:11 +0100
Date: Tue, 19 May 2015 14:41:11 +0100
From: bug-gcc 
Message-ID: <555b2f67.63d3f...@gnu.org>
To: 
Subject:  adjustment reminder 
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="--090100070701080303090607"
X-CTCH-RefID: re=0.000,recu=0.000,reip=0.000,vtr=0001.0A020203.555A0C13.0294,vl=2,vh,cl=1,cld=1,fgs=0
X-CTCH-VOD: High
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules: 
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-CSC: 0
X-CHA: v=2.1 cv=LKVfHvm9 c=1 sm=1 tr=0 a=cDoOgBah9ZqUdf9C08b/pQ==:117
	a=cDoOgBah9ZqUdf9C08b/pQ==:17 a=mDV3o1hI:8 a=Q3aiujJw:8
	a=g0qM3YM6:8 a=aNC3eoYo:8 a=h1PgugrvaO0A:10
	a=KvXsQYXyHm4_OUjhtv8A:9 a=CjuIK1q_8ugA:10 a=jHfF38WbX7IA:10
	a=G8C09Qyg5MUA:10 a=QwP0Ggf9GeEA:10 a=djkNAb8kAGeZhEbTz2gA:9
	a=ZUQdxo_J7JhUPYoN8LAA:14 a=IKIoO-ieCDEA:10
Received-SPF: softfail (mail61c45: transitioning domain of gnu.org does not designate 85.31.195.58 as permitted sender) client-ip=85.31.195.58; envelope-from=bug-...@gnu.org;
X-WHL: LR


Delivery status notification

2015-05-19 Thread Mail Delivery System
  This is an automatically generated Delivery Status Notification.  

Delivery to the following recipients failed permanently:

   * karaughm...@chello.sk


Reporting-MTA: dns; edge02.upcmail.net [192.168.14.72]
Received-From-MTA: dns; gnu.org [85.31.195.58]
Arrival-Date: Tue, 19 May 2015 14:41:31 +0200


Final-recipient: rfc822; karaughmore@chello.sk
Action: failed
Status: 5.1.1
Diagnostic-Code: smtp;  550 Invalid recipient: 
Last-attempt-Date: Tue, 19 May 2015 14:41:31 +0200


X-SourceIP: 85.31.195.58
Received: from dK5pH.gnu.org (dK5pH.gnu.org [112.121.185.196])
	by 9CihNm.com (Postfix) with ESMTP id 57C9D40165
	for ; Tue, 19 May 2015 14:41:28 +0100 (CEST)
Received: from [123.107.194.197] by m7uZ.6k5YRJLV.gnu.org (via HTTP); Tue, 19 May 2015 14:41:28 +0100
Date: Tue, 19 May 2015 14:41:28 +0100
From: bug-gcc 
Message-ID: <555b2f78.a5247...@gnu.org>
To: 
Subject:  adjustment reminder 
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="--050400060205050807010401"




Returned mail: see transcript for details

2015-05-19 Thread Mail Delivery Subsystem
The original message was received at Tue, 19 May 2015 08:41:35 -0400
from cpe-et001203.cust.jaguar-network.net [85.31.195.58]

   - The following addresses had permanent fatal errors -
jerikawil...@gmail.com
(reason: 552-5.7.0 This message was blocked because its content presents a 
potential)
(expanded from: jeri...@vantex.com)
tcastan...@gmail.com
(reason: 552-5.7.0 This message was blocked because its content presents a 
potential)
(expanded from: ter...@vantex.com)
roberta.s.barr...@gmail.com
(reason: 552-5.7.0 This message was blocked because its content presents a 
potential)
(expanded from: robe...@vantex.com)
alistairmelli...@gmail.com
(reason: 552-5.7.0 This message was blocked because its content presents a 
potential)
(expanded from: alist...@vantex.com)

   - Transcript of session follows -
... while talking to gmail-smtp-in.l.google.com.:
>>> DATA
<<< 552-5.7.0 This message was blocked because its content presents a potential
<<< 552-5.7.0 security issue. Please visit
<<< 552-5.7.0 http://support.google.com/mail/bin/answer.py?answer=6590 to 
review our
<<< 552 5.7.0 message content and attachment content guidelines. 
y14si8922486vdi.26 - gsmtp
554 5.0.0 Service unavailable
Reporting-MTA: dns; mail58c28.carrierzone.com
Received-From-MTA: DNS; cpe-et001203.cust.jaguar-network.net
Arrival-Date: Tue, 19 May 2015 08:41:35 -0400

Original-Recipient: rfc822;probe@vantex.com
Final-Recipient: RFC822; probe@vantex.com
X-Actual-Recipient: RFC822; jerikawild18@gmail.com
Action: failed
Status: 5.7.0
Remote-MTA: DNS; gmail-smtp-in.l.google.com
Diagnostic-Code: SMTP; 552-5.7.0 This message was blocked because its content presents a potential
Last-Attempt-Date: Tue, 19 May 2015 08:41:42 -0400

Original-Recipient: rfc822;probe@vantex.com
Final-Recipient: RFC822; probe@vantex.com
X-Actual-Recipient: RFC822; tcastano80@gmail.com
Action: failed
Status: 5.7.0
Remote-MTA: DNS; gmail-smtp-in.l.google.com
Diagnostic-Code: SMTP; 552-5.7.0 This message was blocked because its content presents a potential
Last-Attempt-Date: Tue, 19 May 2015 08:41:42 -0400

Original-Recipient: rfc822;probe@vantex.com
Final-Recipient: RFC822; probe@vantex.com
X-Actual-Recipient: RFC822; roberta.s.barrera@gmail.com
Action: failed
Status: 5.7.0
Remote-MTA: DNS; gmail-smtp-in.l.google.com
Diagnostic-Code: SMTP; 552-5.7.0 This message was blocked because its content presents a potential
Last-Attempt-Date: Tue, 19 May 2015 08:41:42 -0400

Original-Recipient: rfc822;probe@vantex.com
Final-Recipient: RFC822; probe@vantex.com
X-Actual-Recipient: RFC822; alistairmelliott@gmail.com
Action: failed
Status: 5.7.0
Remote-MTA: DNS; gmail-smtp-in.l.google.com
Diagnostic-Code: SMTP; 552-5.7.0 This message was blocked because its content presents a potential
Last-Attempt-Date: Tue, 19 May 2015 08:41:42 -0400
X-Envelope-From: bug-...@gnu.org
Return-Path: 
Received: from gnu.org (cpe-et001203.cust.jaguar-network.net [85.31.195.58])
	by mail58c28.carrierzone.com (8.14.9/8.13.1) with ESMTP id t4JCfVlj029732
	for ; Tue, 19 May 2015 08:41:35 -0400
Received: from t26aq.gnu.org (t26aq.gnu.org [143.141.119.124])
	by DBblJH.com (Postfix) with ESMTP id 57C9D40165
	for ; Tue, 19 May 2015 14:41:33 +0100 (CEST)
Received: from [148.194.126.119] by Oky7.nfeW8WLZ.gnu.org (via HTTP); Tue, 19 May 2015 14:41:33 +0100
Date: Tue, 19 May 2015 14:41:33 +0100
From: bug-gcc 
Message-ID: <555b2f7d.3b46d...@gnu.org>
To: 
Subject:  adjustment reminder 
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="--030309010606090902090106"
X-CTCH-RefID: re=0.000,recu=0.000,reip=0.000,vtr=0001.0A020201.555A0C11.0211,vl=2,vh,cl=1,cld=1,fgs=0
X-CTCH-VOD: High
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules: 
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-CSC: 0
X-CHA: v=2.1 cv=T9G1EZ6Q c=1 sm=1 tr=0 a=cDoOgBah9ZqUdf9C08b/pQ==:117
	a=cDoOgBah9ZqUdf9C08b/pQ==:17 a=mDV3o1hI:8 a=Q3aiujJw:8
	a=g0qM3YM6:8 a=NTMjfisW:8 a=h1PgugrvaO0A:10
	a=KvXsQYXyHm4_OUjhtv8A:9 a=CjuIK1q_8ugA:10 a=jHfF38WbX7IA:10
	a=G8C09Qyg5MUA:10 a=QwP0Ggf9GeEA:10 a=djkNAb8kAGeZhEbTz2gA:9
	a=ZUQdxo_J7JhUPYoN8LAA:14 a=IKIoO-ieCDEA:10
Received-SPF: softfail (mail58c28: transitioning domain of gnu.org does not designate 85.31.195.58 as permitted sender) client-ip=85.31.195.58; envelope-from=bug-...@gnu.org;
X-WHL: LR


Mail Delivery Failure

2015-05-19 Thread Mail Delivery System
This message was created automatically by the mail system (ecelerity).

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

>>> qaqf6k84.6297...@bm-eng.com (after RCPT TO): 550-5.1.1 The email account 
>>> that you tried to reach does not exist. Please try
550-5.1.1 double-checking the recipient's email address for typos or
550-5.1.1 unnecessary spaces. Learn more at
550 5.1.1 http://support.google.com/mail/bin/answer.py?answer=6596 
n10si8271748igv.28 - gsmtp
Reporting-MTA: dns; mx01.tds.cmh.synacor.com
Arrival-Date: Tue, 19 May 2015 08:41:31 -0400

Last-Attempt-Date: Tue, 19 May 2015 08:41:31 -0400
Status: 5.1.1
Action: failed
Final-Recipient: rfc822; qaqf6k84.6297902@bm-eng.com
Remote-MTA: dns; 74.125.193.27
Diagnostic-Code: smtp; 550-5.1.1 The email account that you tried to reach does not exist. Please try
550-5.1.1 double-checking the recipient's email address for typos or
550-5.1.1 unnecessary spaces. Learn more at
550 5.1.1 http://support.google.com/mail/bin/answer.py?answer=6596 n10si8271748igv.28 - gsmtp
-- This is a copy of the headers of the original message. --

Return-Path: 
x-binding: premig.tds.net
X_CMAE_Category: , ,
X-CNFS-Analysis: v=2.0 cv=YZg/Fntf c=1 sm=1 a=cDoOgBah9ZqUdf9C08b/pQ==:17 
a=mDV3o1hI:8 a=h1PgugrvaO0A:10 a=KvXsQYXyHm4_OUjhtv8A:9 a=CjuIK1q_8ugA:10 
a=MBg09A6m2oIA:10 a=G8C09Qyg5MUA:10 a=QwP0Ggf9GeEA:10 a=EhOF20fBXaCFw14a3dgA:9 
a=IKIoO-ieCDEA:10 a=cDoOgBah9ZqUdf9C08b/pQ==:117
X-CM-Score: 0
X-Scanned-by: Cloudmark Authority Engine
Received: from [85.31.195.58] ([85.31.195.58:30924] helo=gnu.org)
by mx.tds.net (envelope-from )
(ecelerity 3.5.1.37854 r(Momo-dev:3.5.1.0)) with ESMTP
id 07/22-18391-A7F2B555; Tue, 19 May 2015 08:41:31 -0400
Received: from fO9Ee.gnu.org (fO9Ee.gnu.org [144.187.190.103])
by Xupwgj.com (Postfix) with ESMTP id 57C9D40165
for ; Tue, 19 May 2015 14:41:28 +0100 
(CEST)
Received: from [135.144.195.111] by zIPT.kunQz1oM.gnu.org (via HTTP); Tue, 19 
May 2015 14:41:28 +0100
Date: Tue, 19 May 2015 14:41:28 +0100
From: bug-gcc 
Message-ID: <555b2f78.28b9f...@gnu.org>
To: 
Subject:  adjustment reminder 
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="--040508010704080604010002"




Message Notification

2015-05-19 Thread Mail Delivery System
The following email message was  blocked by an email content filter because it 
may contain executable files.  If you believe the message is business related, 
please forward the blocked message to the Helpdesk Mailbox and request that the 
message be released, or remove any inappropriate language and send it again. If 
 no contact is made within 5 days the message will be automatically deleted. 

Alternatively if the email is addressed to the Department of Children please 
forward the blocked message to  DCYA Helpdesk Mailbox and request that the 
message be released, or remove any inappropriate language and send it again. If 
 no contact is made within 5 days the message will be automatically deleted


Message details are..
DATE: 05/19/15
TIME: 19 May 2015 13:41:26 +0100
SUBJECT: [SPAM] adjustment reminder 
RECIPIENT: 
Dropped File Types: None
Dropped File Names: None





RFC822/M400 Mail Network -- Delivery Report

2004-10-31 Thread Mail Delivery Subsystem
Not delivered to: [EMAIL PROTECTED]
user agent unavailable
Original-Envelope-Id: in*vsnl*rfc987;41859fb972e5000mimey2k
X400-Content-Identifier: 041101080017+053
Reporting-MTA: x400; /ADMD=VSNL/C=IN
DSN-Gateway: smtp; terminator1.vsnl.net.in

Final-Recipient: rfc822;
	[EMAIL PROTECTED]
Action: failed
Diagnostic-Code: x400; 1 4
Status: 5.1.1
Last-Attempted-Date: 1  Nov 2004 07:57 +0530
X-Supplementary: Hello World

RFC822/M400 Mail Network -- Delivery Report

2004-11-19 Thread Mail Delivery Subsystem
Not delivered to: [EMAIL PROTECTED]
bad address
Original-Envelope-Id: in*vsnl*rfc987;419ee9ca43a5000mimey2k
X400-Content-Identifier: 041120122258+053
Reporting-MTA: x400; /ADMD=VSNL/C=IN
DSN-Gateway: smtp; terminator1.vsnl.net.in

Final-Recipient: rfc822;
	[EMAIL PROTECTED]
Action: failed
Diagnostic-Code: x400; 1 0
Status: 5.1.1
Last-Attempted-Date: 20 Nov 2004 12:09 +0530

Mail delivery failed: returning message to sender

2024-07-09 Thread Mail Delivery System
This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  gcc-bugs@gcc.gnu.org
host gcc.gnu.org [8.43.85.97]
SMTP error from remote mail server after end of data:
550 5.7.1 Blocked by SpamAssassin
Reporting-MTA: dns; server18.fedenet.gr

Action: failed
Final-Recipient: rfc822;gcc-bugs@gcc.gnu.org
Status: 5.0.0
Remote-MTA: dns; gcc.gnu.org
Diagnostic-Code: smtp; 550 5.7.1 Blocked by SpamAssassin


Mail delivery failed: returning message to sender

2024-10-03 Thread Mail Delivery System
This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of
its recipients. This is a permanent error.

The following address failed:

dennis.drisc...@verizon.net:
SMTP error from remote server for TEXT command, host: 
mx-aol.mail.gm0.yahoodns.net (67.195.228.86) reason: 552 1 Requested mail 
action aborted, mailbox not found


--- The header of the original message is following. ---

Received: from winhex19beus6.winusa.mail ([10.72.152.143]) by
 mrieueus.server.lan (mrieueus004 [172.19.150.82]) with ESMTPS (Nemesis) id
 0M0OyJ-1s2UVT2e9F-016xQ0 for ; Thu, 03 Oct 2024
 17:38:50 +0200
Received: from [100.127.255.249] (10.72.152.251) by winhex19beus2.winusa.mail
 (10.72.152.141) with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.2.1544.11; Thu, 3 Oct
 2024 11:38:49 -0400
From: Notification SRC-65dc4def-e41e-4484-a47a-1d6b427d86ef

To: 
Subject: NeTfLIX
Message-ID: <172796991933.5292.12155405605174255...@gcc.gnu.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="373i202410y24077"
Return-Path: gcc-bugs@gcc.gnu.org
Date: Thu, 3 Oct 2024 11:38:49 -0400
X-ClientProxiedBy: winhex19beus2.winusa.mail (10.72.152.141) To
 winhex19beus2.winusa.mail (10.72.152.141)
X-Spam-Flag: NO
UI-OutboundReport: notjunk:1;M01:P0:ua/IrYhkYpE=;zfdijWQR8139IJF2AqX/Fq0HaD4
 XCRaYkPOKhp9u+c8Lj685vgj3WL1pvxy0DA/97ihNRdhBcSdSQSQADI9/wGQlRaUpCf52UAqh
 YUIaI+B/RVesMbc3EYVxMQ32OXINc5uFCDIl9Al/zUgL5HiW1j+LALHKio9So/417mpwpYWe1
 zMbY6YXYAjztf/ZFm3f7cV+FjVjKXJdtGLDOdSM6WiJyQM3GkFN1BrPdZnpBFjfUkQWDimvA+
 ZL3EoXnbu3nZG5+FUwT7RIaS3a/V0QaoiPZp8UJptpC+LzFKkblgq2+WrGYYopw4VryMcsHiy
 Lj6t+DX48Ef+ThRKzNqgAu6LZ/J4X5UNLk8rLTO7w0/O+i8xpv/MpUje+51aBEhlnQ4/RhfY/
 +ASRs4li1TGDCOBmftIAcVyCZE420Ii/dXnpl+vQq5PFXU9KVX319nA1RVsg6PR9OktErX7jQ
 HuyABun1auOse/i6bOFrLFsJ6ng/9xJlripYaBccingJTOCWeEv/MQgqw2uNgi/wBRZaMI5E3
 YwZHTHgc2W+dpNYYX3vRcC+OqPLwuvSnPnFXL2eF6Uo321Vrl6wzkoRUVTsQSVY+azyLNcIIP
 HQpOtHg5DjNQk6aebRAmgYZjQptZ820AQh2W8I7bKQH5IsaHpcVBw92HhSKEY0nNpOSctE0CA
 TS8EP1ihu0bb3ipHYVjQy2BcNgn4FYHOGeyoXzM7MbLBlPlPPsc+hsfd3xeH2ceOBe7KuqCM5
 k6Sp8JqqzjrJYAFqcVe353ET8jiyf+8iw==
Reporting-MTA: dns;perfora.net
Arrival-Date: Thu, 03 Oct 2024 17:38:50 +0200

Final-Recipient: rfc822;dennis.driscoll@verizon.net
Action: failed
Status: 5.0.0
Final-Log-ID: 0M0OyJ-1s2UVT2e9F-016xQ0
Received: from winhex19beus6.winusa.mail ([10.72.152.143]) by
 mrieueus.server.lan (mrieueus004 [172.19.150.82]) with ESMTPS (Nemesis) id
 0M0OyJ-1s2UVT2e9F-016xQ0 for ; Thu, 03 Oct 2024
 17:38:50 +0200
Received: from [100.127.255.249] (10.72.152.251) by winhex19beus2.winusa.mail
 (10.72.152.141) with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.2.1544.11; Thu, 3 Oct
 2024 11:38:49 -0400
From: Notification SRC-65dc4def-e41e-4484-a47a-1d6b427d86ef
	
To: 
Subject: NeTfLIX
Message-ID: <172796991933.5292.12155405605174255...@gcc.gnu.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="373i202410y24077"
Return-Path: gcc-bugs@gcc.gnu.org
Date: Thu, 3 Oct 2024 11:38:49 -0400
X-ClientProxiedBy: winhex19beus2.winusa.mail (10.72.152.141) To
 winhex19beus2.winusa.mail (10.72.152.141)
X-Spam-Flag: NO
UI-OutboundReport: notjunk:1;M01:P0:ua/IrYhkYpE=;zfdijWQR8139IJF2AqX/Fq0HaD4
 XCRaYkPOKhp9u+c8Lj685vgj3WL1pvxy0DA/97ihNRdhBcSdSQSQADI9/wGQlRaUpCf52UAqh
 YUIaI+B/RVesMbc3EYVxMQ32OXINc5uFCDIl9Al/zUgL5HiW1j+LALHKio9So/417mpwpYWe1
 zMbY6YXYAjztf/ZFm3f7cV+FjVjKXJdtGLDOdSM6WiJyQM3GkFN1BrPdZnpBFjfUkQWDimvA+
 ZL3EoXnbu3nZG5+FUwT7RIaS3a/V0QaoiPZp8UJptpC+LzFKkblgq2+WrGYYopw4VryMcsHiy
 Lj6t+DX48Ef+ThRKzNqgAu6LZ/J4X5UNLk8rLTO7w0/O+i8xpv/MpUje+51aBEhlnQ4/RhfY/
 +ASRs4li1TGDCOBmftIAcVyCZE420Ii/dXnpl+vQq5PFXU9KVX319nA1RVsg6PR9OktErX7jQ
 HuyABun1auOse/i6bOFrLFsJ6ng/9xJlripYaBccingJTOCWeEv/MQgqw2uNgi/wBRZaMI5E3
 YwZHTHgc2W+dpNYYX3vRcC+OqPLwuvSnPnFXL2eF6Uo321Vrl6wzkoRUVTsQSVY+azyLNcIIP
 HQpOtHg5DjNQk6aebRAmgYZjQptZ820AQh2W8I7bKQH5IsaHpcVBw92HhSKEY0nNpOSctE0CA
 TS8EP1ihu0bb3ipHYVjQy2BcNgn4FYHOGeyoXzM7MbLBlPlPPsc+hsfd3xeH2ceOBe7KuqCM5
 k6Sp8JqqzjrJYAFqcVe353ET8jiyf+8iw==


[Bug c++/105512] compilation with -fmodules-ts and std=c++20 leads to segfault

2023-09-08 Thread mail--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105512

Gerrit Albrecht  changed:

   What|Removed |Added

 CC||m...@gerrit-albrecht.de

--- Comment #2 from Gerrit Albrecht  ---
Hi. I can confirm both reports. Tried it with "g++.exe (Rev2, Built by MSYS2
project) 13.2.0" MinGW64 compiler; both -std=c++23 and -std=c++20 segfault
together with -fmodules-ts. It works without -std option and with
D_GLIBCXX_USE_CXX11_ABI=0. Thanks.

[Bug c++/38173] New: Mistake in Russian translation of error text "functional cast expression list treated as compound expression"

2008-11-18 Thread rilium at mail dot ru
Hello

I've found that there is mistake in translation of this error message:
LANG=C make
...
error: functional cast expression list treated as compound expression
...

[EMAIL PROTECTED]:~/Spectra_Project/libspectra$ echo "Current LANG: "$LANG
&& make
Current LANG: ru_RU.UTF-8
...
îøèáêà: functional cast - ñïèñîå âûðàæåíèé ðàññìàòðèâàåòñÿ êàê ñîñòàâíîå
âûðàæåíèå
...

Here in word "ñïèñîå", last symbol must be 'ê', someone mistaked while typed in
this text

My system: Debian lenny
gcc version:
[EMAIL PROTECTED]:~/Spectra_Project/libspectra$ LANG=C gcc -v
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.3.2-1'
--with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs
--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared
--with-system-zlib --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3
--program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug
--enable-objc-gc --enable-mpfr --enable-targets=all --enable-cld
--enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu
--target=i486-linux-gnu
Thread model: posix
gcc version 4.3.2 (Debian 4.3.2-1)


-- 
   Summary: Mistake in Russian translation of error text "functional
cast expression list treated as compound expression"
   Product: gcc
   Version: 4.3.2
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: rilium at mail dot ru


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38173



[Bug c/38310] New: -ftree-parallelize-loops=4 causes ICE with gcc-4.3.2

2008-11-28 Thread nickols_k at mail dot ru
I tried to compile mplayerxp with -ftree-parallelize-loops=4 and gcc produced
ICE:

gcc -m64 -c -march=amdfam10 -O3 -funroll-all-loops -ffast-math
-fprefetch-loop-arrays -ftree-parallelize-loops=4 -mmmx -m3dnow -msse -msse2
-msse3 -msse4a -mabm -mcx16 -msahf  --param l1-cache-line-size=64 --param
l1-cache-size=128 --param l2-cache-size=512 -mfpmath=387,sse -mfancy-math-387
-mveclibabi=acml -finline-functions-called-once -funit-at-a-time -pipe -fopenmp
-fopenmp -ftree-parallelize-loops=4 -I/usr/X11/include -I/usr/X11R6/include  -W
-Wall -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-D__USE_FILE_OFFSET64 -D__USE_LARGEFILE -D_LARGEFILE64_SOURCE -I. -I..
-I../../codecs/libavutil -Wall -o af_format.o af_format.c
af_format.c: In function 'play._loopfn.6':
af_format.c:382: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.


-- 
   Summary: -ftree-parallelize-loops=4 causes ICE with gcc-4.3.2
   Product: gcc
   Version: 4.3.2
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: nickols_k at mail dot ru
 GCC build triplet: x86_64-unknown-linux
  GCC host triplet: x86_64-unknown-linux
GCC target triplet: x86_64-unknown-linux


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38310



[Bug c/38310] -ftree-parallelize-loops=4 causes ICE with gcc-4.3.2

2008-11-28 Thread nickols_k at mail dot ru


--- Comment #1 from nickols_k at mail dot ru  2008-11-28 18:20 ---
Created an attachment (id=16791)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16791&action=view)
preprocessed input which causes ICE with -ftree-parallelize-loop=4


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38310



[Bug c++/38501] New: typedef confuses the name of the template and the name of result

2008-12-11 Thread resume755 at mail dot ru
typedef confuses the name of the template and the name of result:

sh-3.2$ cat tloop_iterator.h
#ifndef TLOOP_ITERATOR_H_
#define TLOOP_ITERATOR_H_

#include 

template
struct loop_iterator : public T::iterator
{ };


template 
struct list : std::list
{
  typedef loop_iterator loop_iterator;
};

#endif

Compiling this file:

sh-3.2$ g++-4.1  tloop_iterator.h
sh-3.2$ g++-4.2  tloop_iterator.h

all right, but:

sh-3.2$ g++-4.3  tloop_iterator.h
tloop_iterator.h:14: error: declaration of ‘typedef struct
loop_iterator > list::loop_iterator’
tloop_iterator.h:8: error: changes meaning of ‘loop_iterator’ from ‘struct
loop_iterator >’

sh-3.2$ g++-4.3 --version
g++-4.3 (Debian 4.3.2-1) 4.3.2
Copyright (C) 2008 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

My system is Debian GLU/Linux Lenny

Version 4.3.1 also has this problem


-- 
   Summary: typedef confuses the name of the template and the name
of result
   Product: gcc
   Version: 4.3.2
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: resume755 at mail dot ru


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38501



[Bug c++/38501] typedef confuses the name of the template and the name of result

2008-12-11 Thread resume755 at mail dot ru


--- Comment #1 from resume755 at mail dot ru  2008-12-12 01:42 ---
Created an attachment (id=16896)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16896&action=view)
demo


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38501



[Bug target/38900] ICE: unable to find a register to spill

2009-06-25 Thread ivmai at mail dot ru


--- Comment #4 from ivmai at mail dot ru  2009-06-25 10:31 ---
Bug confirmed in mingw-w64 gcc v4.5.0 (32-bit target).
Bug also observed in MinGW gcc v3.4.5 and v4.2.1


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38900



[Bug libstdc++/40939] New: unordered_map insertion generates seg fault

2009-08-02 Thread comm_wolf at mail dot ru
Compiler details:
Target: mingw32
Configured with: ../../configure --prefix=/mingw --host=mingw32
--target=mingw32 --program-prefix= --with-as=/mingw/bin/
as.exe --with-ld=/mingw/bin/ld.exe --with-gcc --with-gnu-ld --with-gnu-as
--enable-threads --disable-nls --enable-langua
ges=c,c++ --disable-win32-registry --disable-shared --without-x
--enable-interpreter --enable-hash-synchronization --ena
ble-libstdcxx-debug --with-gmp-include=/projects/common/GMP/4.3.1
--with-gmp-lib=/projects/common/GMP/4.3.1/.libs --with
-mpfr-include=/projects/common/MPFR/2.4.1
--with-mpfr-lib=/projects/common/MPFR/2.4.1/.libs
Thread model: win32
gcc version 4.5.0 20090421 (experimental - lambda branch) (GCC)

Insertion into std::tr1::unordered_map generates segmentation fault. Here is
code sample:

#include 
#include 
#include 
#include 
#include 
#include 

class ABC
{
public:
ABC() : m_A(0) {;}
ABC(int a) : m_A(a) {;}
int A() const {return m_A;}
bool operator ==(ABC const& other) const {return m_A == other.m_A;}
private:
int m_A;

friend std::ostream& operator << (std::ostream& os, ABC const& obj)
{
os << obj.m_A;
return os;
}
};

struct hash_ABC : std::unary_function
{
size_t operator()(ABC const& v) const {return v.A();}
};

int main()
{
typedef std::unordered_map dict_t;

dict_t dic;

ABC key(2);

dic.insert(std::make_pair(ABC(1), std::string("One")));
dic.insert(std::make_pair(key, std::string("Two")));
dic.insert(std::make_pair(ABC(3), std::string("Three")));

return 0;
}

My own investigations were shown what problem is within _M_allocate_node
function (include\c++\tr1_impl\hashtable, line #477). When I removed
__try/__catch block from this function all start work fine. In the original
case this function returns strange value (sometimes NULL, sometimes garbage).


-- 
   Summary: unordered_map insertion generates seg fault
   Product: gcc
   Version: 4.5.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: libstdc++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: comm_wolf at mail dot ru
 GCC build triplet: i386-pc-mingw
  GCC host triplet: i386-pc-mingw
GCC target triplet: i386-pc-mingw


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40939



[Bug libstdc++/40939] unordered_map insertion generates seg fault

2009-08-02 Thread comm_wolf at mail dot ru


--- Comment #1 from comm_wolf at mail dot ru  2009-08-02 11:04 ---
Created an attachment (id=18285)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18285&action=view)
Preprocessed sample source file


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40939



[Bug libstdc++/40939] unordered_map insertion generates seg fault

2009-08-02 Thread comm_wolf at mail dot ru


--- Comment #3 from comm_wolf at mail dot ru  2009-08-02 11:38 ---
Ok. I'll try it.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40939



[Bug libstdc++/40939] unordered_map insertion generates seg fault

2009-08-02 Thread comm_wolf at mail dot ru


--- Comment #5 from comm_wolf at mail dot ru  2009-08-02 17:52 ---
Thanks for your advise.

After gcc recompilation (according to the currently trunk state) error was
disappeared. It seems like there is a bug in 'lambda' branch sources.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40939



[Bug c++/24189] crash at exit after dlclose with -fuse-cxa-atexit

2005-11-27 Thread hidden_peak at mail dot ru


--- Comment #13 from hidden_peak at mail dot ru  2005-11-27 16:41 ---
This is really bug in glibc: __cxa_finalize don't call all registered handlers
in case of NULL argument (glibc 2.2.5 has this bug, but 2.3.2 already not).

But nevertheless, the problem still present at platforms without glibc.

Really, I wonder why code specific for C++ language support (and even more:
specific for gcc) should be in glibc? May be the better place is one of crt*.o?


-- 

hidden_peak at mail dot ru changed:

   What|Removed |Added

 CC||hidden_peak at mail dot ru


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24189



[Bug c++/24189] crash at exit after dlclose with -fuse-cxa-atexit

2005-11-27 Thread hidden_peak at mail dot ru


--- Comment #14 from hidden_peak at mail dot ru  2005-11-27 16:48 ---
Created an attachment (id=10348)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10348&action=view)
__cxa_atexit and __cxa_finalize that work correctly

cxa.c contain code with __cxa_atexit and __cxa_finalize that work correctly
with gcc 3.4.x (really I am check only 3.4.4). Useful when builded as so
library and used in LD_PRELOAD to fix glibc problem.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24189



[Bug c++/24189] crash at exit after dlclose with -fuse-cxa-atexit

2005-11-27 Thread hidden_peak at mail dot ru


--- Comment #16 from hidden_peak at mail dot ru  2005-11-27 17:40 ---
Thanks for explanation. Link to this issue:
http://www.codesourcery.com/cxx-abi/abi.html#dso-dtor (for archive/reference
purposes).


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24189



[Bug c++/28539] New: granted access to private nested class

2006-07-29 Thread dushistov at mail dot ru
g++ compile such code without any warrnings:

class C {
private:
class N {
public:
N(int val) { this->value = val; }
int getValue() { return value; }
private:
int value;
};
N nO;
public:
C() : nO(17) {}
N &getNestedPrivateObject() {
return nO;
}
};


int main() 
{
C o;
return o.getNestedPrivateObject().getValue();
}


-- 
   Summary: granted access to private nested class
   Product: gcc
   Version: 4.1.1
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dushistov at mail dot ru


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28539



[Bug c++/28543] New: Usage of -ftemplate-depth- may cause segfault

2006-07-30 Thread dushistov at mail dot ru
$ cat fac.cpp 
#include 

template  struct f;
template<> struct f<0> { enum { value = 1 }; };
template<> struct f<1> { enum { value = 1 }; };
template  struct f { enum { value = n * f::value }; };

int main()
{
printf("%u\n", f<-10>::value);
return 0;
}

$ LANG=en_EN g++ -ftemplate-depth-1 fac.cpp
g++: Internal error: Segmentation fault (program cc1plus)


-- 
   Summary: Usage of  -ftemplate-depth- may cause segfault
   Product: gcc
   Version: 4.1.1
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dushistov at mail dot ru


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28543



[Bug c++/28586] New: thowing exception before main() leads to crash on AIX

2006-08-03 Thread bigwad at mail dot ru
test enviroment: AIX 5.2, 5.3; gcc 3.3.2, 4.1.0

code to reproduce:
int f()
{
  try
  {
throw 1;
  }
  catch(int){}

  return 0;
}

int i = f();

int main( int argc, char* argv[] )
{
  return 0;
}


-- 
   Summary: thowing exception before main() leads to crash on AIX
   Product: gcc
   Version: 4.1.0
Status: UNCONFIRMED
  Severity: major
  Priority: P3
 Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: bigwad at mail dot ru


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28586



[Bug c++/28588] New: static private function

2006-08-03 Thread dushistov at mail dot ru
$ cat test.cpp 
class Foo { static void f() {} };

int main()
{
Foo foo;
void (*f)();
f = foo.f;
return 0;
}

$ g++ -Wall test.cpp && echo "success"
success

If trying compile it with another compiler
http://cpp.sourceforge.net/?show=18471
I got something like this:

ComeauTest.c(7): error: function "Foo::f" is inaccessible
  f = foo.f;


-- 
   Summary: static private function
   Product: gcc
   Version: 4.1.1
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
    ReportedBy: dushistov at mail dot ru


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28588



[Bug c/30695] New: uint32_t -> uint16_t without warrnings

2007-02-03 Thread dushistov at mail dot ru
$cat gcc-wrap.c
#include 
#include 

int main()
{
uint32_t a = 1 << 17;
uint16_t b = a;
printf("a: %u, b: %u\n", (unsigned)a, (unsigned)b);
return 0;
}
$gcc -Wall -Wextra -Wconversion -pedantic gcc-wrap.c
no warrnings
$gcc --version
gcc (GCC) 4.1.1
for example:
$icc --version
iccbin (ICC) 9.1 20060706
$icc -Wall gcc-wrap.c 
gcc-wrap.c(7): remark #810: conversion from "uint32_t={unsigned int}" to
"uint16_t={unsigned short}" may lose significant bits
uint16_t b = a;
 ^


-- 
   Summary: uint32_t -> uint16_t without warrnings
   Product: gcc
   Version: unknown
Status: UNCONFIRMED
  Severity: enhancement
  Priority: P3
 Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dushistov at mail dot ru


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30695



[Bug c/30695] uint32_t -> uint16_t without warrnings

2007-02-03 Thread dushistov at mail dot ru


--- Comment #2 from dushistov at mail dot ru  2007-02-03 21:15 ---
(In reply to comment #1)
> I think this has already been fixed on the trunk with the new -Wconversion
> behaviors:
> http://gcc.gnu.org/wiki/NewWconversion
> 

Thaks for reply, 
I hope to see this feature in near future.


-- 

dushistov at mail dot ru changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||FIXED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30695



[Bug c/31007] New: wrong 64bit constant calculation

2007-03-01 Thread hidden_peak at mail dot ru
#include 
#include 

int main()
{ 
  uint64_t ui4 = ~((1ULL << 63ULL) >> 3ULL);
  union {
   uint64_t i64;
   struct {
 uint32_t lo;
 uint32_t hi;
   } i32;
  } ui5;

  ui5.i64 = ui4;

  printf( "%llx %x\n", ui4, ui5.i32.hi );

  return 0;
}

Return efff efff
(instead of 7fff 7fff). Appropriate expression for 32bit
constant give expected result.


-- 
   Summary: wrong 64bit constant calculation
   Product: gcc
   Version: 4.1.1
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: hidden_peak at mail dot ru
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31007



[Bug c/31007] wrong 64bit constant calculation

2007-03-01 Thread hidden_peak at mail dot ru


--- Comment #1 from hidden_peak at mail dot ru  2007-03-01 12:30 ---
> (instead of 7fff 7fff)

Correct should be fff and fff.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31007



[Bug c/31007] wrong 64bit constant calculation

2007-03-01 Thread hidden_peak at mail dot ru


--- Comment #3 from hidden_peak at mail dot ru  2007-03-01 14:48 ---
~((1ULL << 63ULL) >> 3ULL):

(   0001 << 63) -> 8000    (unsigned!)
(8000    >> 3 ) -> f000    (due to sign bit)
~(f000   )  -> 0fff   ffff

Right?


-- 

hidden_peak at mail dot ru changed:

   What|Removed |Added

 Status|RESOLVED|UNCONFIRMED
 Resolution|INVALID |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31007



[Bug c/31007] wrong 64bit constant calculation

2007-03-01 Thread hidden_peak at mail dot ru


--- Comment #5 from hidden_peak at mail dot ru  2007-03-01 15:05 ---
Do you mean this treatment: ~((1ULL << 63ULL) >> 3ULL) -> ~(1ULL << 60ULL) ->
efff ?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31007



[Bug c/31007] wrong 64bit constant calculation

2007-03-01 Thread hidden_peak at mail dot ru


--- Comment #6 from hidden_peak at mail dot ru  2007-03-01 15:11 ---
> Shifting unsigned numbers doesn't replicate the sign bit.

unsigned ui3 = ~((1 << 31) >> 3);

printf( "%x\n", ui3 );

give me wrong result fff ?


-- 

hidden_peak at mail dot ru changed:

   What|Removed |Added

 Status|RESOLVED|UNCONFIRMED
 Resolution|INVALID |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31007



[Bug c/31007] wrong 64bit constant calculation

2007-03-01 Thread hidden_peak at mail dot ru


--- Comment #7 from hidden_peak at mail dot ru  2007-03-01 15:13 ---
My mistake. Sorry.


-- 

hidden_peak at mail dot ru changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31007



[Bug c++/16625] Discarded Linkonce sections in .rodata

2007-03-05 Thread hidden_peak at mail dot ru


--- Comment #38 from hidden_peak at mail dot ru  2007-03-05 14:53 ---
(In reply to comment #37)
> 
> Can I reproduce it on Linux?
> 

May be comment #21 help you?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16625



[Bug c++/31180] New: Bad cpp condition in gcc/unwind-pe.h

2007-03-14 Thread bland at mail dot ru
There is a minor problem in file:
http://gcc.gnu.org/viewcvs/trunk/gcc/unwind-pe.h?revision=101317&view=markup

/* If using C++, references to abort have to be qualified with std::.  */
-#if __cplusplus
+#ifdef __cplusplus
#define __gxx_abort std::abort


-- 
   Summary: Bad cpp condition in gcc/unwind-pe.h
   Product: gcc
   Version: unknown
Status: UNCONFIRMED
  Severity: minor
  Priority: P3
 Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: bland at mail dot ru


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31180



[Bug other/31180] Bad cpp condition in gcc/unwind-pe.h

2007-03-14 Thread bland at mail dot ru


--- Comment #2 from bland at mail dot ru  2007-03-15 06:00 ---
I did not say that is bad. That is wrong and produces annoying warning.
Which can easily turn into error when reused in -Werror clean code.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31180



[Bug c/31291] New: Different (wrong?) behaviour using ffps when enabling optimizing

2007-03-20 Thread mail at sebastianbauer dot info
The purpose of the attached code is to print out the internal representation of
some floating points. However, when compiling with optimizations turned on the
behaviour of the compiled program is not the expected one (i.e. the proper hex
representation is not printed out, but something else, here 0). I encounter
this behaviour on amd64 debian as on windows using cygwin gcc.

I'm going to attach the debian output of compilation and invocation.


-- 
   Summary: Different (wrong?) behaviour using ffps when enabling
optimizing
   Product: gcc
   Version: 4.1.2
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: mail at sebastianbauer dot info
 GCC build triplet: x86_64
  GCC host triplet: x86_64
GCC target triplet: x86_64


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31291



[Bug c/31291] Different (wrong?) behaviour using ffps when enabling optimizing

2007-03-20 Thread mail at sebastianbauer dot info


--- Comment #1 from mail at sebastianbauer dot info  2007-03-21 07:14 
---
Created an attachment (id=13240)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13240&action=view)
The simple test source.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31291



[Bug c/31291] Different (wrong?) behaviour using ffps when enabling optimizing

2007-03-20 Thread mail at sebastianbauer dot info


--- Comment #2 from mail at sebastianbauer dot info  2007-03-21 07:15 
---
Created an attachment (id=13241)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13241&action=view)
The output of the compiler invocation and the executable.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31291



[Bug java/32774] New: GCJ dumps core when semicolon placed to wrong place (x86, arm_le)

2007-07-16 Thread cyberflex at mail dot ru
This code makes GCJ-4.1 core dump because of presence
unneeded (or incorrect) ";" symbol after the method definition
close brace:

interface MyInterface {
public Object dumpGCJCoreAtCompilation();
}

class MyClass implements MyInterface{

public Object dumpGCJCoreAtCompilation(){return null;};


}


This code compiled fine:

class MyClass {

public Object dumpGCJCoreAtCompilation(){return null;}


}


-- 
   Summary: GCJ dumps core when semicolon placed to wrong place
(x86, arm_le)
   Product: gcc
   Version: 4.1.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: java
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: cyberflex at mail dot ru


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32774



[Bug java/32774] GCJ dumps core when semicolon placed to wrong place (x86, arm_le)

2007-07-16 Thread cyberflex at mail dot ru


--- Comment #2 from cyberflex at mail dot ru  2007-07-16 09:42 ---
(In reply to comment #1)
> I think this was fixed in 4.3 by using the Eclipse source compiler.
> 

Well, thnks.
This just need to be verified.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32774



[Bug java/33218] New: Process.waiFor() Process.destroy() misbehave for childs which are not reacting to Ctrl+C SIGQUIT

2007-08-28 Thread cyberflex at mail dot ru
When creating process (Process p = ...) which do not respond to Ctrl+C
then behavior of destroy or waitFor or both is incorrect.

Process blocking/discarding signal sent by Ctrl+C is not killed by destroy().
(The Process.destroy() supposed (IMHO) to kill the child process forcibly.)

After calling destroy() other method waitFor() returns immediately instead of
waiting (survived after the signal) process completion forever.

Such behavior looks to be such  a discrepancy.


Test case:
I encounted the problem when used following command line
rfcomm listen -i hci0 /dev/rfcomm0 6

rfcomm doesn't react to Ctrl+C till external connection is accepted.

Program code:

Process p =
p.destroy();
p.waitFor()
System.out.println("waitFor completed");





ps ax | grep rfcomm


Workaround for application:
kill such processes explicitly with "kill -9" or
kill subchildren of shell scripts by themselves using shell "trap" command.


Not sure that the issue exists in 4.2.x, I haven't one to test with
architectures I use.


-- 
   Summary: Process.waiFor() Process.destroy() misbehave for childs
which are not reacting to Ctrl+C SIGQUIT
   Product: gcc
   Version: 4.1.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: java
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: cyberflex at mail dot ru
  GCC host triplet: arm_le, x86 - native compilation


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33218



[Bug java/33218] Process.waiFor() Process.destroy() misbehave for childs which are not reacting to Ctrl+C SIGQUIT

2007-08-28 Thread cyberflex at mail dot ru


--- Comment #2 from cyberflex at mail dot ru  2007-08-28 16:43 ---
(In reply to comment #1)
> Can you post a fully self contained test case?  If I can easily reproduce it, 
> I
> will try to fix it.
> 

Test case is to be following, but reproducing looks like to be a bit tricky :(
gcj (GCC) 4.1.2 20061115 (prerelease) (SUSE Linux) doesn't show such behaviour,
I'll try (in a few days) this once more with my real scripts and real hardware
platfrom that compiler. Then I'll post more detailed report to this bug.

May be the problem is observed only when script is sleep in syscall only.
Yet I could kill script manually, so it might not be a kernel issue.




test.java

import java.lang.*;

public class test{

public static void main(String[] args) throws Exception{
 String cmd = "./test.sh";
 Process p = Runtime.getRuntime().exec(cmd);
 p.destroy();
 p.waitFor();
 System.out.println("waitFor completed");
 while(1 == 1){
  Thread.currentThread().sleep(3000);
 }
}


}


test.sh:


#!/bin/bash


trap "" SIGINT
trap "" SIGQUIT



Thanks.


-- 

cyberflex at mail dot ru changed:

   What|Removed |Added

 CC||cyberflex at mail dot ru


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33218



[Bug java/33218] Process.waiFor() Process.destroy() misbehave for childs which are not reacting to Ctrl+C SIGQUIT

2007-08-29 Thread cyberflex at mail dot ru


--- Comment #6 from cyberflex at mail dot ru  2007-08-29 10:16 ---
(In reply to comment #4)
> Created an attachment (id=14129)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14129&action=view) [edit]
> Test case that works.
> 
> With the new "Test case that works" and attached test.sh and the original
> test.sh I get no failures on x86_64-pc-linux  (FC6)  with: gcj (GCC) 4.3.0
> 20070728 (experimental) 
> 
> I am inclined to mark the bug as Works-for-me in a few days if it cannot be
> reproduced on the trunk.
> 
Ok, that's need more investigation.
I'll be working on my project again (choosing workaround) in a few days,
I'll investigate in more detail the situation when I see the issue at both
architectures.

I no mean to reproduce is found (till the middle of the next week) then the bug
may be reopened as a good testcase would be produced.

Thank you for looking through current code.
In GCJ 3.x.x we had a couple of troubles with zombie childs may be some
nonetrivial case is not swept pou yet.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33218



[Bug java/33218] Process.waiFor() Process.destroy() misbehave for childs which are not reacting to Ctrl+C SIGQUIT

2007-08-30 Thread cyberflex at mail dot ru


--- Comment #7 from cyberflex at mail dot ru  2007-08-30 09:34 ---
Problem is reproducible, but it likely should be posted to other list.
It looks that behaviour of particular utility "rfcomm" is such specific that
it not only ignores some signals but also forks one more child in detached
state.

Here how I do reproduce it:

As root do

1. attach my USB bluetooth dondle and bring it  up "hciconfig hci0 up"
2. run "./test"
3. run "ps ax | grep rfcomm"
Very soon I see that the only instance of rfcomm is running (PID is not
changed) and instances of rfcomm started later are exiting because interface
hci0 is busy.



Some processes still need SIGINT due to notify their children before exiting or
be killed with other signal such as -9

The bug, posted here looks like needs resolution as INVALID.
Oh, I terribly sorry

What do you think?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33218



[Bug java/33218] Process.waiFor() Process.destroy() misbehave for childs which are not reacting to Ctrl+C SIGQUIT

2007-08-30 Thread cyberflex at mail dot ru


--- Comment #8 from cyberflex at mail dot ru  2007-08-30 09:34 ---
Created an attachment (id=14139)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14139&action=view)
test.java

test.java to run with bt_connect.bash


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33218



[Bug java/33218] Process.waiFor() Process.destroy() misbehave for childs which are not reacting to Ctrl+C SIGQUIT

2007-08-30 Thread cyberflex at mail dot ru


--- Comment #9 from cyberflex at mail dot ru  2007-08-30 09:35 ---
Created an attachment (id=14140)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14140&action=view)
script bt_connect.bash

script to use with 14139: test.java


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33218



[Bug java/33218] Process.waiFor() Process.destroy() misbehave for childs which are not reacting to Ctrl+C SIGQUIT

2007-08-30 Thread cyberflex at mail dot ru


--- Comment #10 from cyberflex at mail dot ru  2007-08-30 09:36 ---
Created an attachment (id=14141)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14141&action=view)
one more helper script bt_param.bash

helper script for  14139: test.java


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33218



[Bug java/33218] Process.waiFor() Process.destroy() misbehave for childs which are not reacting to Ctrl+C SIGQUIT

2007-08-30 Thread cyberflex at mail dot ru


--- Comment #11 from cyberflex at mail dot ru  2007-08-30 09:41 ---
It looks that the fact that, rfcomm in some situations are killed when shell
script called with Proces.destroy() and in some situations don't
misleded me.
Also the strace shows that rfcomm sleep inside accept system call.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33218



[Bug java/33218] Process.waiFor() Process.destroy() misbehave for childs which are not reacting to Ctrl+C SIGQUIT

2007-08-31 Thread cyberflex at mail dot ru


--- Comment #13 from cyberflex at mail dot ru  2007-08-31 09:42 ---
(In reply to comment #12)
> Does GCJ's behavior differ from Sun's in this test?
> 

Well.. tried that (jdk1.6 i386)
Answer is: at this point NOT. So this is "not an issue"

But while performing this test I found a slight difference
in treating of output streams of process for which the waitFor returned.

GCJ-compiled program may use output stream of such process: use available(),
read(), readLine() e.t.c.
In out case readLine() returns null

While JDK-compiled class running in SUN's JVM (both are 1.6 version) throws
exception:
Exception in thread "main" java.io.IOException: Stream closed
at
java.io.BufferedInputStream.getInIfOpen(BufferedInputStream.java:134)
at java.io.BufferedInputStream.available(BufferedInputStream.java:381)
at java.io.FilterInputStream.available(FilterInputStream.java:142)
at test.main(test.java:19)


This looks like to be a slight deviation from standard in GCJ :(

But that's NOT the problem I stated initially and is to be dealt in othe bug
(IMHO)

When running shell script the rfcomm program replaces it in process list
(accordingly POSIX or something likes that) so I always erroniously considered
not killed rfcomm as NOT killed bt_connect.sh

I feal myself ashamed, I apologize once again ;)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33218



[Bug c/33374] New: GCC 4.1.2 produce wrong assembler code with -O2 option enabled.

2007-09-10 Thread _kirpichev_ at mail dot ru
I use gcc 4.1.2 under solaris and linux and compile code using next commands:
Linux:
gcc -pipe -Wall -Wextra -Winvalid-pch -ansi -pedantic -Wundef -Wc++-compat
-Wfloat-equal -Wredundant-decls -Waggregate-return -Wbad-function-cast
-Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wcast-align
-Wshadow -Wsign-compare -Wnested-externs -Wcast-qual -Wpointer-arith
-Wdeclaration-after-statement -Werror -O2 -finline-functions
-Wdisabled-optimization -DNDEBUG test.c -o mtest_l

Solaris:
gcc -pipe -Wall -Wextra -Winvalid-pch -ansi -pedantic -Wundef -Wc++-compat
-Wfloat-equal -Wredundant-decls -Waggregate-return -Wbad-function-cast
-Wstrict-prototypes -Wcast-align -Wshadow -Wsign-compare -Wnested-externs
-Wcast-qual -Wpointer-arith -Wdeclaration-after-statement -Werror -O2
-finline-functions -Wdisabled-optimization -DNDEBUG -g -o mtest test.c

Segmentation fault happens when I try to run test program (see test.c
attached).


-- 
   Summary: GCC 4.1.2 produce wrong assembler code with -O2 option
enabled.
   Product: gcc
   Version: 4.1.2
Status: UNCONFIRMED
  Severity: critical
  Priority: P3
 Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: _kirpichev_ at mail dot ru


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33374



[Bug c/33374] GCC 4.1.2 produce wrong assembler code with -O2 option enabled.

2007-09-10 Thread _kirpichev_ at mail dot ru


--- Comment #1 from _kirpichev_ at mail dot ru  2007-09-10 07:45 ---
Created an attachment (id=14182)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14182&action=view)
test programm

This example is compiled incorrectly by gcc 4.1.2 with -O2 flag.
But all works fine if we change line 93 in this example on next:
XML_Remove(currNode_sp);


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33374



[Bug c/33374] GCC 4.1.2 produce wrong assembler code with -O2 option enabled.

2007-09-10 Thread _kirpichev_ at mail dot ru


--- Comment #2 from _kirpichev_ at mail dot ru  2007-09-10 07:53 ---
Created an attachment (id=14183)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14183&action=view)
Correct and incorrect assembler dumps.

>From incorrect dump we can see where segmentation fault heppens:

0x0804839e :   movDWORD PTR [ecx+4],0x0
0x080483a5 :   movDWORD PTR [eax+4],edx
0x080483a8 :   movedx,DWORD PTR [ecx+4]
0x080483ab :   movecx,ebx
0x080483ad :   movDWORD PTR [edx],eax

Instruction 0x080483ad tries to dereferencing pointer in edx, but
in edx zero was put by 0x080483a8.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33374



[Bug target/33374] GCC 4.1.2 produce wrong assembler code with -O2 option enabled.

2007-09-10 Thread _kirpichev_ at mail dot ru


--- Comment #4 from _kirpichev_ at mail dot ru  2007-09-10 08:53 ---
There is no core dump with -fno-strict-aliasing.
But, our code is used by others who can not set this option.
Should code compiled without -fno-strict-aliasing produce core dump?
In my opinion, the best way is produce only compiliation warnings in this case.

Should we rewrite our code if it is not possible to set -fno-strict-aliasing
option, or it is gcc issue that fixed in other versions?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33374



[Bug c++/37480] New: GCC Allows null-references in C++

2008-09-11 Thread rarut at mail dot ru
It's possible to create null references which contradicts the standard:

Assume simple structs:

template
struct null_val {
null_val(T t = T()) : value(t) {}
T value;
};

template
struct null_ref : null_val {};

Now it's possible to use 'null_ref().value' which is null reference!


-- 
   Summary: GCC Allows null-references in C++
   Product: gcc
   Version: 4.2.2
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: rarut at mail dot ru


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37480



[Bug c++/37480] GCC Allows null-references in C++

2008-09-11 Thread rarut at mail dot ru


--- Comment #1 from rarut at mail dot ru  2008-09-11 11:45 ---
Generally reference members when used like this seem to behaive like pointers:
- have default constructor (making null reference)
- store garbage when when left uninitialized


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37480



[Bug c/37975] New: Incorrect argument checking for printf: "format not a string literal, argument types not checked", where it can be checked

2008-10-30 Thread rilium at mail dot ru
rintf__, 3,
4)));

extern int vsnprintf (char *__restrict __s, size_t __maxlen,
__const char *__restrict __format, __gnuc_va_list __arg)
 __attribute__ ((__nothrow__)) __attribute__ ((__format__ (__printf__, 3,
0)));

# 398 "/usr/include/stdio.h" 3 4





extern int fscanf (FILE *__restrict __stream,
 __const char *__restrict __format, ...) ;




extern int scanf (__const char *__restrict __format, ...) ;

extern int sscanf (__const char *__restrict __s,
 __const char *__restrict __format, ...) __attribute__ ((__nothrow__));
# 441 "/usr/include/stdio.h" 3 4

# 504 "/usr/include/stdio.h" 3 4





extern int fgetc (FILE *__stream);
extern int getc (FILE *__stream);





extern int getchar (void);

# 528 "/usr/include/stdio.h" 3 4
extern int getc_unlocked (FILE *__stream);
extern int getchar_unlocked (void);
# 539 "/usr/include/stdio.h" 3 4
extern int fgetc_unlocked (FILE *__stream);











extern int fputc (int __c, FILE *__stream);
extern int putc (int __c, FILE *__stream);





extern int putchar (int __c);

# 572 "/usr/include/stdio.h" 3 4
extern int fputc_unlocked (int __c, FILE *__stream);







extern int putc_unlocked (int __c, FILE *__stream);
extern int putchar_unlocked (int __c);






extern int getw (FILE *__stream);


extern int putw (int __w, FILE *__stream);








extern char *fgets (char *__restrict __s, int __n, FILE *__restrict __stream)
 ;






extern char *gets (char *__s) ;

# 653 "/usr/include/stdio.h" 3 4





extern int fputs (__const char *__restrict __s, FILE *__restrict __stream);





extern int puts (__const char *__s);






extern int ungetc (int __c, FILE *__stream);






extern size_t fread (void *__restrict __ptr, size_t __size,
   size_t __n, FILE *__restrict __stream) ;




extern size_t fwrite (__const void *__restrict __ptr, size_t __size,
size_t __n, FILE *__restrict __s) ;

# 706 "/usr/include/stdio.h" 3 4
extern size_t fread_unlocked (void *__restrict __ptr, size_t __size,
 size_t __n, FILE *__restrict __stream) ;
extern size_t fwrite_unlocked (__const void *__restrict __ptr, size_t __size,
  size_t __n, FILE *__restrict __stream) ;








extern int fseek (FILE *__stream, long int __off, int __whence);




extern long int ftell (FILE *__stream) ;




extern void rewind (FILE *__stream);

# 742 "/usr/include/stdio.h" 3 4
extern int fseeko (FILE *__stream, __off_t __off, int __whence);




extern __off_t ftello (FILE *__stream) ;
# 761 "/usr/include/stdio.h" 3 4






extern int fgetpos (FILE *__restrict __stream, fpos_t *__restrict __pos);




extern int fsetpos (FILE *__stream, __const fpos_t *__pos);
# 784 "/usr/include/stdio.h" 3 4

# 793 "/usr/include/stdio.h" 3 4


extern void clearerr (FILE *__stream) __attribute__ ((__nothrow__));

extern int feof (FILE *__stream) __attribute__ ((__nothrow__)) ;

extern int ferror (FILE *__stream) __attribute__ ((__nothrow__)) ;




extern void clearerr_unlocked (FILE *__stream) __attribute__ ((__nothrow__));
extern int feof_unlocked (FILE *__stream) __attribute__ ((__nothrow__)) ;
extern int ferror_unlocked (FILE *__stream) __attribute__ ((__nothrow__)) ;








extern void perror (__const char *__s);






# 1 "/usr/include/bits/sys_errlist.h" 1 3 4
# 27 "/usr/include/bits/sys_errlist.h" 3 4
extern int sys_nerr;
extern __const char *__const sys_errlist[];
# 823 "/usr/include/stdio.h" 2 3 4




extern int fileno (FILE *__stream) __attribute__ ((__nothrow__)) ;




extern int fileno_unlocked (FILE *__stream) __attribute__ ((__nothrow__)) ;
# 842 "/usr/include/stdio.h" 3 4
extern FILE *popen (__const char *__command, __const char *__modes) ;





extern int pclose (FILE *__stream);





extern char *ctermid (char *__s) __attribute__ ((__nothrow__));
# 882 "/usr/include/stdio.h" 3 4
extern void flockfile (FILE *__stream) __attribute__ ((__nothrow__));



extern int ftrylockfile (FILE *__stream) __attribute__ ((__nothrow__)) ;


extern void funlockfile (FILE *__stream) __attribute__ ((__nothrow__));
# 912 "/usr/include/stdio.h" 3 4

# 4 "test.c" 2
void f(const char* str1, const char* str2)
{
 const char* fmt = "Something is: %s, and something another is: %s\n";
 const size_t buff_len = strlen(fmt) + strlen(str1) + strlen(str2) + 1;
 char* buff = (char*)malloc(buff_len);
 sprintf(buff, fmt, "Str1", "str2");

 free(buff);

}

int main()
{
 return 0;
}


-- 
   Summary: Incorrect argument checking for printf: "format not a
string literal, argument types not checked", where it
can be checked
   Product: gcc
   Version: 4.3.2
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: rilium at mail dot ru


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37975



[Bug c/37975] Incorrect argument checking for printf: "format not a string literal, argument types not checked", where it can be checked

2008-10-30 Thread rilium at mail dot ru


--- Comment #1 from rilium at mail dot ru  2008-10-31 02:11 ---
Created an attachment (id=16593)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16593&action=view)
Preproccessed file test.c


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37975



[Bug c++/34886] New: Strangeness of name lookup in template function

2008-01-20 Thread rvovsd at mail dot ru
On compiling that code:

--- begin code ---
class Y {};

void f(Y*) { } // line 3. If comment - all ok

template < typename T>
void sel(T* a) { f(a); } //line 6

void f(void*) {}

int main(int argc, char **argv)
{
sel((void*)0); //line 12
}
--- end code ---

Àppears error:
../main.cpp: In function ‘void sel(T*) [with T = void]’:
../main.cpp:12:   instantiated from here
../main.cpp:6: error: invalid conversion from ‘void*’ to ‘Y*’
../main.cpp:6: error:   initializing argument 1 of ‘void f(Y*)’

If comment line 3, then work.
Also work, if line 3 move after line 6.

If functions f(Y*), f(void*) and sel(T*) placed in different header files, then
arise dependency on order including headers.


-- 
   Summary: Strangeness of name lookup in template function
   Product: gcc
   Version: 4.2.1
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: rvovsd at mail dot ru
  GCC host triplet: openSuse 10.3


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34886



[Bug c++/34893] New: Strangeness of name lookup in template function

2008-01-20 Thread rvovsd at mail dot ru
On compiling that code:

--- begin code ---
class Y {};

void f(Y*) { } // line 3. If comment - all ok

template < typename T>
void sel(T* a) { f(a); } //line 6

void f(void*) {}

int main(int argc, char **argv)
{
sel((void*)0); //line 12
}
--- end code ---

Àppears error:
../main.cpp: In function ‘void sel(T*) [with T = void]’:
../main.cpp:12:   instantiated from here
../main.cpp:6: error: invalid conversion from ‘void*’ to ‘Y*’
../main.cpp:6: error:   initializing argument 1 of ‘void f(Y*)’

If comment line 3, then work.
Also work, if line 3 move after line 6.

If functions f(Y*), f(void*) and sel(T*) placed in different header files, then
arise dependency on order including headers.


-- 
   Summary: Strangeness of name lookup in template function
   Product: gcc
   Version: 4.2.1
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: rvovsd at mail dot ru
  GCC host triplet: openSuse 10.3


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34893



[Bug c++/34886] Strangeness of name lookup in template function

2008-01-21 Thread rvovsd at mail dot ru


--- Comment #3 from rvovsd at mail dot ru  2008-01-21 14:43 ---
This case is similar to the bug 31047
(http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31047).

There Andrew Pinski wrote (comment 4):
>14.6.4.2/1 says this is invalid code.
>For a function call that depends on a template parameter, if the function is an
>unqualified-id but not a template-id, the candiate functions are found using
>the usual lookup rules (3.4.1, 3.4.2) except that:
>
>
>Paraphasing since I don't want to type it all in
>* non argument dependent lookup (3.4.1: template definition context
>* argument dependent lookup (3.4.2):  template definition context and template
>instation context

This case is argument dependent lookup, therefore should used both contexts -
definition and instantiation.
Point of instantiation "sel(T* a) with T = void" - after "void f(void*)" and
before "int main()".
Thus should be visible both f(void*) and f(Y*), whether not so?
Why gcc does not see "void f (void *)"?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34886



[Bug libstdc++/39738] New: GCC cannot build itself for win64 platform

2009-04-11 Thread css20 at mail dot ru
pe_traits:228:
error: previous definition of 'struct std::is_function<_Res ()(_ArgTypes ...)>'
/usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/tr1_impl/type_traits:248:
error: invalid qualifiers on non-member function type
/usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/tr1_impl/type_traits:248:
error: redefinition of 'struct std::is_function<_Res ()(_ArgTypes ..., ...)>'
/usr/portage/local/overlays/build/x86_64-pc-mingw32/libstdc++-v3/include/tr1_impl/type_traits:231:
error: previous definition of 'struct std::is_function<_Res ()(_ArgTypes ...,
...)>'

Affected versions - 4.4.0 prerelease and top-of-tree(4.5.0), gcc 4.3.3 builds
itself for win64 without any problems.


-- 
   Summary: GCC cannot build itself for win64 platform
   Product: gcc
   Version: 4.4.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: libstdc++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: css20 at mail dot ru
 GCC build triplet: x86_64-pc-linux-gnu
  GCC host triplet: x86_64-pc-mingw32
GCC target triplet: x86_64-pc-mingw32


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39738



[Bug target/39738] GCC cannot build itself for win64 platform

2009-04-11 Thread css20 at mail dot ru


--- Comment #3 from css20 at mail dot ru  2009-04-11 21:09 ---
> Are you sure your entire compiler is up to date, not just the library?
No.. it was not lasest snapshot (20090331).

> We solve this by setting up in gcc's source tree a symbolic link "winsup" 
> pointing to the sysroot (prefix) directory

I move to gcc-4.4.0-20090407, create symbolik link to my prefix directory
(/usr/win64), but build not successfully..

make running from build/x86_64-pc-mingw32/libstdc++-v3/src:

/bin/sh ../libtool --tag CXX --mode=compile x86_64-pc-mingw32-c++
-L/usr/portage/local/overlays/gcc-4.4.0/build/x86_64-pc-mingw32/winsup/mingw
-L/usr/portage/local/overlays/gcc-4.4.0/build/x86_64-pc-mingw32/winsup/w32api/lib
-isystem /usr/portage/local/overlays/gcc-4.4.0/src/winsup/mingw/include
-isystem /usr/portage/local/overlays/gcc-4.4.0/src/winsup/w32api/include 
-I/usr/portage/local/overlays/gcc-4.4.0/build/x86_64-pc-mingw32/libstdc++-v3/include/x86_64-pc-mingw32
-I/usr/portage/local/overlays/gcc-4.4.0/build/x86_64-pc-mingw32/libstdc++-v3/include
-I/usr/portage/local/overlays/gcc-4.4.0/src/libstdc++-v3/libsupc++ 
-fno-implicit-templates -Wall -Wextra -Wwrite-strings -Wcast-qual 
-fdiagnostics-show-location=once  -ffunction-sections -fdata-sections  -g -O2  
 -std=gnu++0x -c ../../../../src/libstdc++-v3/src/atomic.cc
libtool: compile:  x86_64-pc-mingw32-c++
-L/usr/portage/local/overlays/gcc-4.4.0/build/x86_64-pc-mingw32/winsup/mingw
-L/usr/portage/local/overlays/gcc-4.4.0/build/x86_64-pc-mingw32/winsup/w32api/lib
-isystem /usr/portage/local/overlays/gcc-4.4.0/src/winsup/mingw/include
-isystem /usr/portage/local/overlays/gcc-4.4.0/src/winsup/w32api/include
-I/usr/portage/local/overlays/gcc-4.4.0/build/x86_64-pc-mingw32/libstdc++-v3/include/x86_64-pc-mingw32
-I/usr/portage/local/overlays/gcc-4.4.0/build/x86_64-pc-mingw32/libstdc++-v3/include
-I/usr/portage/local/overlays/gcc-4.4.0/src/libstdc++-v3/libsupc++
-fno-implicit-templates -Wall -Wextra -Wwrite-strings -Wcast-qual
-fdiagnostics-show-location=once -ffunction-sections -fdata-sections -g -O2
-std=gnu++0x -c ../../../../src/libstdc++-v3/src/atomic.cc -o atomic.o
In file included from
/usr/portage/local/overlays/gcc-4.4.0/build/x86_64-pc-mingw32/libstdc++-v3/include/utility:88,
 from
/usr/portage/local/overlays/gcc-4.4.0/build/x86_64-pc-mingw32/libstdc++-v3/include/tuple:43,
 from
/usr/portage/local/overlays/gcc-4.4.0/build/x86_64-pc-mingw32/libstdc++-v3/include/mutex:44,
 from ../../../../src/libstdc++-v3/src/atomic.cc:33:
/usr/portage/local/overlays/gcc-4.4.0/src/libstdc++-v3/libsupc++/initializer_list:
In constructor 'std::initializer_list<_E>::initializer_list()':
/usr/portage/local/overlays/gcc-4.4.0/src/libstdc++-v3/libsupc++/initializer_list:59:
error: 'NULL' was not declared in this scope

There is a possibility of manual build.. call make with these options
make -j9 CFLAGS="-g -O2 -DNULL=0" CXXFLAGS="-g -O2 -DNULL=0

and compile remaining parts of gcc from root build directory, but it is not too
convenient...


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39738



[Bug target/39738] GCC cannot build itself for win64 platform

2009-04-12 Thread css20 at mail dot ru


--- Comment #4 from css20 at mail dot ru  2009-04-12 08:50 ---
First tests of Win64 compiler.. simple source file test.c was created:

#include "windows.h"

int main(int argc, char **argv)
{
  MessageBox(NULL, "test", "test", MB_OK);
}

E:\temp\test>gcc test.c
gcc: CreateProcess: No such file or directory

E:\temp\test>gcc -### test.c
Using built-in specs.
Target: x86_64-pc-mingw32
Configured with: ../src/configure --prefix=/usr/win64 --with-sysroot=/usr/win64
--host=x86_64-pc-mingw32 --target=x86_64-pc-mingw32 --enable-languages=c,c++
--d
isable-win32-registry --disable-nls --disable-shared --disable-sjlj-exceptions
-
-with-dwarf2 --disable-libssp --enable-libgomp
Thread model: win32
gcc version 4.4.0 20090407 (prerelease) (GCC)
COLLECT_GCC_OPTIONS='-mtune=generic'
 "e:/mingw64/bin/../libexec/gcc/x86_64-pc-mingw32/4.4.0/cc1.exe" "-quiet"
"-ipre
fix" "e:\\mingw64\\bin\\../lib/gcc/x86_64-pc-mingw32/4.4.0/" "test.c" "-quiet"
"
-dumpbase" "test.c" "-mtune=generic" "-auxbase" "test" "-o"
"C:\\Users\\X\\AppDa
ta\\Local\\Temp\\cciH4k6g.s"
COLLECT_GCC_OPTIONS='-mtune=generic'
 " \"" --> 

then compiler drivers segfaults.. gdb output:

Program received signal SIGSEGV, Segmentation fault.
main (argc=3, argv=0x72120) at ../../src/gcc/gcc.c:6848
6848in ../../src/gcc/gcc.c


code from gcc.c(6848):
  /* Determine if there are any linker input files.  */
  num_linker_inputs = 0;
  for (i = 0; (int) i < n_infiles; i++)
if (explicit_link_files[i] || outfiles[i] != NULL)
  num_linker_inputs++;


(gdb) p outfiles[i]
$12 = 0x72200 "test.c"
(gdb) p explicit_link_files[i]
No symbol "explicit_link_files" in current context - ???

disassembly listing:
0040DB7B  cmp byte ptr [rbx+rcx],0   <--- rbx & rcx = 0
0040DB7F  jne 0040DB88 
0040DB81  cmp qword ptr [rdi+rcx*8],0 
0040DB86  je  0040DB8B 

What is it, incorrect build or compiler driver bug ?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39738



[Bug target/39738] GCC cannot build itself for win64 platform

2009-04-12 Thread css20 at mail dot ru


--- Comment #5 from css20 at mail dot ru  2009-04-12 19:35 ---
I see this bug in compiler driver is already known
(http://sourceforge.net/forum/forum.php?thread_id=3091795&forum_id=723797), it
works only with "-O0". I can't found report about this bug in database.. does
it exists ?

> Well, on 4.4 branch there was a patch introducing the winsup link, which got 
> necessary for building libstdc++. We solve this by setting up in gcc's source 
> tree a symbolic link "winsup" pointing to the sysroot (prefix) directory.


Symbolic link "winsup" to prefix directory with mingw-w64 runtime headers not
works properly with current gcc 4.4.0 snapshot.. for correct build you must
*temporary* remove file "stddef.h" from
${YOUR_PREFIX}/x86_64-pc-mingw32/include because it conflicts with same file in
libstdc++ build directory.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39738



[Bug target/39738] GCC cannot build itself for win64 platform

2009-04-13 Thread css20 at mail dot ru


--- Comment #7 from css20 at mail dot ru  2009-04-13 08:11 ---
> Please make sure, that you have in your gcc source root directory the symbolic
> link "winsup" pointing to your prefix directory. Secondly, make sure you have
> the symbolic link "mingw" in your prefix directory, which has to point to
> x86_64-pc-mingw32 directory.

I use Gentoo Linux x64 as build OS with system compiler gcc 4.3.3,
configuration script arguments you can see in my first post. Both symbolic
links were created.. existing stddef.h file in winsup/mingw/include causes
error: 'NULL' was not declared in this scope during libstdc++ building (see my
earlier post).

> Yes, there is already one. But this bug is work-a-round by a temporary hack in
> our crt. So it shouldn't appear anymore.
Alltimes use -O0 is not the solution.. temporary CRT hacks too. Where I can get
more information about this bug ?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39738



[Bug target/39738] GCC cannot build itself for win64 platform

2009-04-13 Thread css20 at mail dot ru


--- Comment #9 from css20 at mail dot ru  2009-04-13 15:48 ---
> Do you use for native toolchain an fresh initialized directory?
> Which version of toolchain you are using (especially header-set)?
> Do you use --prefix and --with-sysroot options?

I use directory with mingw-64 runtime installed as --prefix= and
--with-sysroot= argument. Toolchain versions:
binutils 2.19.1
gmp 4.2.4
mpfr 2.4.1
CRT and pthreads - last versions from
http://sourceforge.net/project/showfiles.php?group_id=202880

> You can try the following. Remove in your  directory the folder
> lib/gcc/x86_64-pc-mingw32/4.4.0/ and remove in your gcc's build directory the
> x86_64-pc-mingw32 folder. Then do a 'make'

No any changes.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39738



[Bug target/39738] GCC cannot build itself for win64 platform

2009-04-13 Thread css20 at mail dot ru


--- Comment #10 from css20 at mail dot ru  2009-04-13 18:06 ---
I try to build gcc with latest CRT from svn (revision 764) - build is OK. It
seems, snapshot from sourceforge download page(November 15, 2008) not
compatible with gcc 4.4.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39738



[Bug c++/94210] New: ICE in tsubst, at cp/pt.c:15105

2020-03-18 Thread tangyixuan at mail dot dlut.edu.cn
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94210

Bug ID: 94210
   Summary: ICE in tsubst, at cp/pt.c:15105
   Product: gcc
   Version: 10.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c++
  Assignee: unassigned at gcc dot gnu.org
  Reporter: tangyixuan at mail dot dlut.edu.cn
  Target Milestone: ---

Hi, gcc crashes given the following example, while clang compiles normally.
$ cat 1.cpp
template struct X {};

namespace Nested {
  template int f1(X... a);

  int a1 = f1(X(), X());
}

$ g++ -v
Using built-in specs.
COLLECT_GCC=/usr/local/gcc-20200315/bin/g++
COLLECT_LTO_WRAPPER=/usr/local/gcc-20200315/libexec/gcc/x86_64-pc-linux-gnu/10.0.1/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc-10-20200315/configure --prefix=/usr/local/gcc-20200315
--enable-checking=release --enable-languages=c,c++ --disable-multilib
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 10.0.1 20200315 (experimental) (GCC) 

$ g++ -c -std=c++11 1.cpp

1.cpp: In substitution of ‘template int Nested::f1(X...)
[with T = ]’:
1.cpp:6:62:   required from here
1.cpp:6:62: internal compiler error: in tsubst, at cp/pt.c:15105
6 |   int a1 = f1(X(), X());
  |  ^
0x5f0f06 tsubst(tree_node*, tree_node*, int, tree_node*)
../../gcc-10-20200315/gcc/cp/pt.c:15105
0x75dd9a unify_pack_expansion
../../gcc-10-20200315/gcc/cp/pt.c:22534
0x74aff5 unify
../../gcc-10-20200315/gcc/cp/pt.c:23307
0x74a20a unify
../../gcc-10-20200315/gcc/cp/pt.c:23204
0x74ae8b unify
../../gcc-10-20200315/gcc/cp/pt.c:23301
0x75e5da try_class_unification
../../gcc-10-20200315/gcc/cp/pt.c:22298
0x74a744 unify
../../gcc-10-20200315/gcc/cp/pt.c:23338
0x75d248 unify_one_argument
../../gcc-10-20200315/gcc/cp/pt.c:21531
0x75db29 unify_pack_expansion
../../gcc-10-20200315/gcc/cp/pt.c:22546
0x749b80 type_unification_real
../../gcc-10-20200315/gcc/cp/pt.c:21670
0x769684 fn_type_unification(tree_node*, tree_node*, tree_node*, tree_node*
const*, unsigned int, tree_node*, unification_kind_t, int, conversion**, bool,
bool)
../../gcc-10-20200315/gcc/cp/pt.c:21030
0x640da5 add_template_candidate_real
../../gcc-10-20200315/gcc/cp/call.c:3396
0x6414f4 add_template_candidate
../../gcc-10-20200315/gcc/cp/call.c:3481
0x6414f4 add_candidates
../../gcc-10-20200315/gcc/cp/call.c:5834
0x6418f7 add_candidates
../../gcc-10-20200315/gcc/cp/call.c:4482
0x6418f7 perform_overload_resolution
../../gcc-10-20200315/gcc/cp/call.c:4490
0x644525 build_new_function_call(tree_node*, vec**, int)
../../gcc-10-20200315/gcc/cp/call.c:4564
0x77bd5c finish_call_expr(tree_node*, vec**, bool,
bool, int)
../../gcc-10-20200315/gcc/cp/semantics.c:2671
0x71f998 cp_parser_postfix_expression
../../gcc-10-20200315/gcc/cp/parser.c:7427
0x7041ba cp_parser_binary_expression
../../gcc-10-20200315/gcc/cp/parser.c:9519
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.

[Bug c++/93642] [Coroutines] internal compiler error: in expand_expr_addr_expr_1, at expr.c:8070 using co_return

2020-04-06 Thread egor_suvorov at mail dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93642

Egor Suvorov  changed:

   What|Removed |Added

 CC||egor_suvorov at mail dot ru

--- Comment #3 from Egor Suvorov  ---
It looks like GCC chokes if it has to call unusual constructor of `promise`.
E.g. if `get_return_object()` returns `int` and there is `promise(int)`
constructor (with no `coroutine_handle` in sight), same error occurs.

However, if I return `promise` from `get_return_object()` and provide
`promise(const promise&) {}`, GCC does not crash.

[Bug target/95112] New: i386 procedures have prolog endbr32

2020-05-13 Thread akobets at mail dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95112

Bug ID: 95112
   Summary: i386 procedures have prolog endbr32
   Product: gcc
   Version: 9.3.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: akobets at mail dot ru
  Target Milestone: ---

gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu1)

Test file:
===
void test()
{
}
===

Buld:
i686-linux-gnu-gcc -c -fno-PIC -mno-mmx -mno-sse -O2 -fomit-frame-pointer
-ffreestanding -fno-stack-protector --no-exceptions test.c

Result:
i686-linux-gnu-objdump -d test.o

test.o: file format elf32-i386


disassembling section .text:

 :
   0:   f3 0f 1e fb endbr32 
   4:   c3  ret
==
Please help me find way to build clear code.
__attribute__((naked)) do not resolve problem.

[Bug target/95112] i686 procedures have prolog endbr32

2020-05-14 Thread akobets at mail dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95112

--- Comment #2 from Alexander Kobets  ---
Yes, that it.
I am not sure, that CF must be enabled by default, at your discretion.
Thank you.

[Bug libstdc++/95289] New: __gnu_debug::__get_distance is not C++11 constexpr compliant

2020-05-23 Thread andysem at mail dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95289

Bug ID: 95289
   Summary: __gnu_debug::__get_distance is not C++11 constexpr
compliant
   Product: gcc
   Version: 10.1.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: libstdc++
  Assignee: unassigned at gcc dot gnu.org
  Reporter: andysem at mail dot ru
  Target Milestone: ---

The following test case fails to compile in C++11 mode:

#include 
#include 
#include 

void foo()
{
typedef std::istream_iterator is_iter;
std::ifstream ifs1("test.dat");
std::vector data1;
is_iter it1(ifs1), it_end;
std::copy(it1, it_end, std::back_inserter(data1));
}

$ g++ -std=c++11 -D_GLIBCXX_DEBUG

/opt/compiler-explorer/gcc-10.1.0/include/c++/10.1.0/debug/helper_functions.h:108:5:
error: body of 'constexpr' function 'constexpr typename
__gnu_debug::_Distance_traits<_Iterator>::__type
__gnu_debug::__get_distance(_Iterator, _Iterator, std::input_iterator_tag)
[with _Iterator = std::istream_iterator; typename
__gnu_debug::_Distance_traits<_Iterator>::__type = std::pair]' not a return-statement

https://gcc.godbolt.org/z/6Aa1ce

This is a regression since gcc 9.

[Bug c++/91304] maybe_unused attribute ignored on variable declared in if declaration

2020-05-27 Thread fsmoke at mail dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91304

fsmoke  changed:

   What|Removed |Added

 CC||fsmoke at mail dot ru

--- Comment #6 from fsmoke  ---
I am sorry..I am new in gcc bugzilla. But.. i have gcc 9.3 and this issue still
takes a place.

[Bug target/63359] aarch64: 32bit registers in inline asm

2020-06-15 Thread andysem at mail dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63359

andysem at mail dot ru changed:

   What|Removed |Added

 CC||andysem at mail dot ru

--- Comment #14 from andysem at mail dot ru ---
I've been hit by this issue recently.

(In reply to Richard Earnshaw from comment #12)
> We considered that, but it won't work.  For example, in ILP32 address
> registers need to use the X form, but are still 32-bits in size.  There are
> other cases as well where a W or X form is required but that is not the
> natural size of the object.

For the cases where the size needs to be specified explicitly, you can leave
%w1/%x1 syntax. But the default register size, I think, should be chosen based
on the asm argument size.

There is one case where I don't feel like %w1/%x1 syntax is correct, even if
currently accepted. It's when the argument allows an alternative of an
immediate constant:

asm("add %w0, %w1, %w2" : "=r"(r) : "r"(i), "Ir"(j));

Note the last argument. When it is a constant, it doesn't need the "w" prefix,
but it needs one if it is a runtime value.

[Bug target/95750] New: [x86] Use dummy atomic insn instead of mfence in __atomic_thread_fence(seq_cst)

2020-06-18 Thread andysem at mail dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95750

Bug ID: 95750
   Summary: [x86] Use dummy atomic insn instead of mfence in
__atomic_thread_fence(seq_cst)
   Product: gcc
   Version: 10.1.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: andysem at mail dot ru
  Target Milestone: ---

Currently, __atomic_thread_fence(seq_cst) on x86 and x86-64 generates mfence
instruction. A dummy atomic instruction (a lock-prefixed instruction or xchg
with a memory operand) would provide the same sequential consistency guarantees
while being more efficient on most current CPUs. The mfence instruction
additionally orders non-temporal stores, which is not relevant for atomic
operations and are not ordered by seq_cst atomic operations anyway.

Regarding performance, some data is available in Agner Fog's instruction
tables:

https://www.agner.org/optimize/

Also, there is this article:

https://shipilev.net/blog/2014/on-the-fence-with-dependencies/

TL;DR: There is benefit on every CPU except Atom; on Atom there is no
difference.

Regarding the dummy instruction and target memory location, here are some
considerations:

- The lock-prefixed instruction should preferably not alter flags or registers
and should require minimum number of registers.
- The memory location should not be shared with other threads.
- The memory location should likely be in cache.
- The memory location should not alias existing data on the stack, so that we
don't introduce a false data dependency on previous or subsequent instructions.

Based on the above, a good candidate is "lock not" on a dummy variable on the
top of the stack. Note that the variable would be accessible through esp/rsp,
it is likely to be in hot memory and is likely thread-private.

I've implemented this optimization in Boost.Atomic, and a similar optimization
is done in MSVC:

https://github.com/microsoft/STL/pull/740

[Bug target/95750] [x86] Use dummy atomic insn instead of mfence in __atomic_thread_fence(seq_cst)

2020-06-18 Thread andysem at mail dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95750

--- Comment #2 from andysem at mail dot ru ---
gcc 10.1 only optimizes __atomic_store_n(seq_cst) to xchg, but not the fence.

Also, consider applying the same optimization to __sync_synchronize().

[Bug target/95751] New: [aarch64] Consider using ldapr for __atomic_load_n(acquire) on ARMv8.3-RCPC

2020-06-18 Thread andysem at mail dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95751

Bug ID: 95751
   Summary: [aarch64] Consider using ldapr for
__atomic_load_n(acquire) on ARMv8.3-RCPC
   Product: gcc
   Version: 10.1.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: andysem at mail dot ru
  Target Milestone: ---

ARMv8.3-RCPC extension adds new ldapr[b/h] instructions for Load-AcquirePC
semantics that better matches C++ memory order semantics.

In particular, the core ldar instructions will wait until the previous stlr,
even on another address, completes on the same thread. The newer ldapr does not
wait for the previous stlr to complete, unless it is performed on the same
address.

Consider using these new instructions in __atomic_load_n(consume/acquire) when
-march=armv8.3 or higher is specified. Note that __atomic_load_n(relaxed) and
__atomic_load_n(seq_cst) should stay unchanged.

[Bug target/95750] [x86] Use dummy atomic insn instead of mfence in __atomic_thread_fence(seq_cst)

2020-06-18 Thread andysem at mail dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95750

--- Comment #5 from andysem at mail dot ru ---
> Please also read [1] why we avoid -4(%%esp).

I believe, memcheck would complain because the value at -4(%%rsp) would be
uninitialized. This is unfortunate. The workaround could be to initialize it
prior to the atomic operation. This would avoid data dependencies with the
surrounding code.

[Bug target/95750] [x86] Use dummy atomic insn instead of mfence in __atomic_thread_fence(seq_cst)

2020-06-18 Thread andysem at mail dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95750

--- Comment #6 from andysem at mail dot ru ---
Also, I think (%%rsp) can be rather far from the top of the stack if the stack
frame is large. This may mean it's less likely to be in data cache. Having a
dummy variable ensures that it is close to the top.

[Bug pch/64117] warning control #pragmas in precompiled headers are not obeyed for template code

2020-06-24 Thread fsmoke at mail dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64117

fsmoke  changed:

   What|Removed |Added

 CC||fsmoke at mail dot ru

--- Comment #4 from fsmoke  ---
Problem persists in gcc 9.3.

very very sadly

[Bug c++/95948] New: memmove error

2020-06-28 Thread Khram at mail dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95948

Bug ID: 95948
   Summary: memmove error
   Product: gcc
   Version: unknown
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c++
  Assignee: unassigned at gcc dot gnu.org
  Reporter: Khram at mail dot ru
  Target Milestone: ---

Memmove has a mistake. Need like this:

char* memmove( char *A, char *B, int L )//! странности из GCC-10.1
{ char *res=A; if( A>B )while( L-->0 )*A++=*B++; else
 { A+=L; B+=L; while( L-->0 )*--A=*--B; } return res;
}

[Bug ipa/96337] [10/11 Regression] GCC 10.2: twice as slow for -O2 -march=x86-64 vs. GCC 9.3/8.4

2020-08-01 Thread andysem at mail dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96337

--- Comment #13 from andysem at mail dot ru ---
I think, this inliner change needs to be reverted. People expect -O2 to produce
decently optimized binaries, and starting with gcc 10.x it doesn't deliver. -O3
traditionally enabled optimizations that may or may not improve performance
(and historically, sometimes even break code), so most projects don't use it.

If there needs to be an optimization mode that prioritizes compilation speed
then let that be a separate mode, e.g. -O1.

[Bug c++/96652] New: Segmentation fault with instantiate_class_template_1

2020-08-17 Thread tangyixuan at mail dot dlut.edu.cn
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96652

Bug ID: 96652
   Summary: Segmentation fault with instantiate_class_template_1
   Product: gcc
   Version: 10.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c++
  Assignee: unassigned at gcc dot gnu.org
  Reporter: tangyixuan at mail dot dlut.edu.cn
  Target Milestone: ---

g++ crashes on the following code, while clang++ compiles successfully:

$: cat s.cpp

struct A {};
template 
struct B
{
A a;
friend decltype(a);
};

int main()
{
A a;
B b; 
}

$: g++ -std=c++11 -c s.cpp

s.cpp: In instantiation of ‘struct B’:
s.cpp:12:12:   required from here
s.cpp:5:7: internal compiler error: Segmentation fault
5 | A a;
  |   ^
0xc6a68f crash_signal
../../gcc-11-20200628/gcc/toplev.c:328
0x77745a instantiate_class_template_1
../../gcc-11-20200628/gcc/cp/pt.c:11974
0x778202 instantiate_class_template(tree_node*)
../../gcc-11-20200628/gcc/cp/pt.c:12098
0x7a7d8d complete_type(tree_node*)
../../gcc-11-20200628/gcc/cp/typeck.c:137
0x7a7d8d complete_type(tree_node*)
../../gcc-11-20200628/gcc/cp/typeck.c:111
0x6a031b start_decl_1(tree_node*, bool)
../../gcc-11-20200628/gcc/cp/decl.c:5490
0x6b0bef start_decl(cp_declarator const*, cp_decl_specifier_seq*, int,
tree_node*, tree_node*, tree_node**)
../../gcc-11-20200628/gcc/cp/decl.c:5453
0x738d3e cp_parser_init_declarator
../../gcc-11-20200628/gcc/cp/parser.c:20818
0x71c052 cp_parser_simple_declaration
../../gcc-11-20200628/gcc/cp/parser.c:13785
0x71dbdd cp_parser_declaration_statement
../../gcc-11-20200628/gcc/cp/parser.c:13217
0x71e7b0 cp_parser_statement
../../gcc-11-20200628/gcc/cp/parser.c:11523
0x71f5c8 cp_parser_statement_seq_opt
../../gcc-11-20200628/gcc/cp/parser.c:11889
0x71f680 cp_parser_compound_statement
../../gcc-11-20200628/gcc/cp/parser.c:11839
0x735280 cp_parser_function_body
../../gcc-11-20200628/gcc/cp/parser.c:23116
0x735280 cp_parser_ctor_initializer_opt_and_function_body
../../gcc-11-20200628/gcc/cp/parser.c:23167
0x73887d cp_parser_function_definition_after_declarator
../../gcc-11-20200628/gcc/cp/parser.c:29063
0x73975f cp_parser_function_definition_from_specifiers_and_declarator
../../gcc-11-20200628/gcc/cp/parser.c:28979
0x73975f cp_parser_init_declarator
../../gcc-11-20200628/gcc/cp/parser.c:20722
0x71c052 cp_parser_simple_declaration
../../gcc-11-20200628/gcc/cp/parser.c:13785
0x741e16 cp_parser_declaration
../../gcc-11-20200628/gcc/cp/parser.c:13484
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.

[Bug c++/96656] New: Segmentation fault with make_friend_class

2020-08-17 Thread tangyixuan at mail dot dlut.edu.cn
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96656

Bug ID: 96656
   Summary: Segmentation fault with make_friend_class
   Product: gcc
   Version: 10.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c++
  Assignee: unassigned at gcc dot gnu.org
  Reporter: tangyixuan at mail dot dlut.edu.cn
  Target Milestone: ---

Please consider the following code. Clang++ compiles it successfully, while g++
fails:

$: cat s.cpp

struct a{};
template  struct b {
using c=a;
};

class B {
template 
friend class b::c;
};

int main() {
B b;
}

$: g++ -c s.cpp
s.cpp:8:25: internal compiler error: Segmentation fault
8 | friend class b::c;
  | ^
0xc6a68f crash_signal
../../gcc-11-20200628/gcc/toplev.c:328
0x6d01b4 make_friend_class(tree_node*, tree_node*, bool)
../../gcc-11-20200628/gcc/cp/friend.c:400
0x73ef87 cp_parser_template_declaration_after_parameters
../../gcc-11-20200628/gcc/cp/parser.c:29140
0x73f0aa cp_parser_explicit_template_declaration
../../gcc-11-20200628/gcc/cp/parser.c:29388
0x718a29 cp_parser_member_specification_opt
../../gcc-11-20200628/gcc/cp/parser.c:24850
0x718a29 cp_parser_class_specifier_1
../../gcc-11-20200628/gcc/cp/parser.c:23947
0x71a603 cp_parser_class_specifier
../../gcc-11-20200628/gcc/cp/parser.c:24254
0x71a603 cp_parser_type_specifier
../../gcc-11-20200628/gcc/cp/parser.c:17762
0x71b422 cp_parser_decl_specifier_seq
../../gcc-11-20200628/gcc/cp/parser.c:14410
0x71bf41 cp_parser_simple_declaration
../../gcc-11-20200628/gcc/cp/parser.c:13664
0x741e16 cp_parser_declaration
../../gcc-11-20200628/gcc/cp/parser.c:13484
0x742504 cp_parser_translation_unit
../../gcc-11-20200628/gcc/cp/parser.c:4761
0x742504 c_parse_file()
../../gcc-11-20200628/gcc/cp/parser.c:44043
0x80bc8b c_common_parse_file()
../../gcc-11-20200628/gcc/c-family/c-opts.c:1190
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.

[Bug c++/83445] conversion function has too high priority in overload resolution

2020-08-17 Thread karzh at mail dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83445

Alexander Karzhenkov  changed:

   What|Removed |Added

 CC||karzh at mail dot ru

--- Comment #1 from Alexander Karzhenkov  ---
Candidate functions considered by overload resolution are

  Target::Target(Source const&);
  constexpr Target::Target(Target const&);
  constexpr Target::Target(Target&&);

The first one doesn't require any user-defined conversion and therefore should
win.

The bug appears to be fixed in gcc 8, but it occurs again in gcc 9 and later
versions.

[Bug c++/83445] conversion function has too high priority in overload resolution

2020-08-18 Thread karzh at mail dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83445

--- Comment #4 from Alexander Karzhenkov  ---
r269667 concerns initializing an object from prvalue.
Here we have `Target` being initialized from lvalue if type `Source`.

What we can consider as being initialized from prvalue is the argument of copy
constructor. It would get the result of `Source::operator Target()`, but this
can be optimized out here. Such optimization, however, is not a mandatory copy
elision (introduced by C++17). The latter is not applicable to reference
initialization.

The mandatory copy elision also is not applicable to initialization `Target`
from `Source` as they are different types (see [dcl.init], item 17.6.1).

In case of direct initialization the candidates are all constructors of
`Target`, but not the conversion operator of `Source` (see [over.match.ctor]).
One of constructors must be called (but this call can be optimized out). The
question here is about implicit conversion for argument of the constructor.

Overload resolution matches the argument of each constructor against the
initializer (which is lvalue of `Source`). The best match is for `Target(Source
const&)` as it doesn't require any user-defined conversion.

If compiler prefers `Target(Target const&)`, it has to perform copy
initialization of its argument from `Source`. Such copy initialization cannot
be performed without user-defined conversion, so it is worse.

Invoking the constructor `Target(Source const&)` is user-defined conversion
whereas binding `Source const&` to `source` is not. But the constructor is
invoked explicitly; overload resolution only takes into account
argument/parameter match.

  1   2   3   4   5   6   7   8   9   10   >