public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Buck <jbuck@synopsys.com>
To: kriol@fnal.gov (Oleg Krivosheev)
Cc: egcs@cygnus.com (egcs team)
Subject: Re: something wrong with template instantiation mechanics
Date: Fri, 10 Oct 1997 08:51:00 -0000	[thread overview]
Message-ID: <199710100207.TAA06042@atrus.synopsys.com> (raw)
In-Reply-To: <Pine.GSO.3.96.971009153209.6246A-200000@drabble>

> i've tried my code and lloks like tons of
> small inline template functions are not
> instantiated.

I think that this is a consequence of the new rules: you have both
non-template and template abs functions.  Unfortunately, I'm confused
by the new rules and not sure what is really supposed to change; I
also think that there still may be some bugs in the code that implements
them.

  reply	other threads:[~1997-10-10  8:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3439FE5B.53F1D3CC.cygnus.egcs@msu.ru>
1997-10-07  3:15 ` AIX & shared libstdc++ Jason Merrill
1997-10-07  3:48   ` Andrey Slepuhin
1997-10-09  9:26   ` Andrey Slepuhin
1997-10-09 15:14     ` Ian Lance Taylor
1997-10-13  5:05       ` Andrey Slepuhin
1997-10-09 16:31     ` something wrong with template instantiation mechanics Oleg Krivosheev
1997-10-10  8:51       ` Joe Buck [this message]
1997-10-10  8:51         ` Oleg Krivosheev
1997-10-10  8:51           ` Oleg Krivosheev
     [not found]           ` <Pine.GSO.3.96.971009232426.6908A-100000.cygnus.egcs@drabble>
1997-10-10 11:44             ` Jason Merrill
1997-10-10 17:21               ` Oleg Krivosheev
1997-10-10 17:19                 ` Jason Merrill
1997-10-10 11:46         ` Oleg Krivosheev
1997-10-10 20:46           ` Alexandre Oliva
1997-10-10  8:51       ` Joe Buck
     [not found] <orbu0tza3m.fsf@sunsite.dcc.unicamp.br>
1997-10-13 13:41 ` Oleg Krivosheev

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=199710100207.TAA06042@atrus.synopsys.com \
    --to=jbuck@synopsys.com \
    --cc=egcs@cygnus.com \
    --cc=kriol@fnal.gov \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).