Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: Jan Hubicka <jh@suse.cz>
Cc: Mark Kettenis <kettenis@chello.nl>,
	drow@mvista.com, aj@suse.de,  gdb-patches@sources.redhat.com,
	gcc@gcc.gnu.org
Subject: Re: [PATCH] Classify non-POD struct types more or less correctly on AMD64
Date: Mon, 12 Jan 2004 05:37:00 -0000	[thread overview]
Message-ID: <1073885852.3462.24.camel@minax.codesourcery.com> (raw)
In-Reply-To: <20040111132924.GA1964@kam.mff.cuni.cz>


> This seems obviously wrong to me.  If you do have testcase, you may want
> to fill it in GCC bugzilla.  Especially if you can write simple testcase
> that fails when copy constructor is not properly used.
> I hope that Mark or Jason can take a look into this issue themselves.

Jan's advise is exactly correct; you should file a bug report in
Bugzilla and then we can take a look.

-- 
Mark Mitchell <mark@codesourcery.com>
CodeSourcery, LLC


  reply	other threads:[~2004-01-12  5:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-10 18:00 Mark Kettenis
2004-01-10 18:36 ` Daniel Jacobowitz
2004-01-10 18:59   ` Mark Kettenis
2004-01-11  4:10     ` Daniel Jacobowitz
2004-01-11 12:38       ` Mark Kettenis
2004-01-11 13:29         ` Jan Hubicka
2004-01-12  5:37           ` Mark Mitchell [this message]
2004-01-11 15:05         ` Gabriel Dos Reis
2004-03-19  0:09         ` Daniel Jacobowitz
2004-03-09 15:39           ` Daniel Jacobowitz
2004-03-19  0:09           ` Mark Mitchell
2004-03-10  3:38             ` Mark Mitchell
2004-03-10  4:21             ` Daniel Jacobowitz
2004-03-19  0:09               ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1073885852.3462.24.camel@minax.codesourcery.com \
    --to=mark@codesourcery.com \
    --cc=aj@suse.de \
    --cc=drow@mvista.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jh@suse.cz \
    --cc=kettenis@chello.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox