temporaries and the
problem went away (the only cluprit were Pascal strings).
--
Waldek Hebisch
[EMAIL PROTECTED]
th an initializer.
This initialize is a CONSTRUCTOR. One of its components is ADDR_EXPR
of another CONSTRUCTOR.
Now, the question is: should `get_base_var' be extended to handle
CONSTRUCTOR nodes or is ADDR_EXPR of a CONSTRUCTOR forbidden from
getting there?
--
Wald
know if Adrian's idea
is a good one. But I think that his intention was to bring gcc
and gpc development closer together with integration as an ultimate
goal.
--
Waldek Hebisch
[EMAIL PROTECTED]
Robert Dewar wrote:
> Laurent GUERBY wrote:
> > On Mon, 2006-03-13 at 15:31 -0700, Jeffrey A Law wrote:
> >> On Mon, 2006-02-27 at 20:08 +0100, Waldek Hebisch wrote:
> >>
> >>> What do you mean by "abuse"? TYPE_MAX_VALUE means maximal value
&g
Jeffrey A Law wrote:
> On Mon, 2006-02-27 at 20:08 +0100, Waldek Hebisch wrote:
>
> > What do you mean by "abuse"? TYPE_MAX_VALUE means maximal value
> > allowed by given type.
> As long as you're *absolutely* clear that a variable with a
> restricted ra
ou think that such behaviour is "abuse" then why to have sparate
TYPE_MAX_VALUE. How to represent range types so that optimizers
will know about allowed ranges (and use them!)? And how about debug
info?
--
Waldek Hebisch
[EMAIL PROTECTED]
k probe look incompatible
with kernel policy for stack extension).
--
Waldek Hebisch
[EMAIL PROTECTED]
Robert Dewar wrote:
> Waldek Hebisch wrote:
>
> > But there is no need to generate trampolines on the stack. Namely,
> > one can generate code in a separate area. In C this causes problems
> > with garbage collection, which IMHO can be solved, but requre alloca-like
>
ents, and providing the rest at call time.
There is some connestion with objects: "partial applicatin" can produce
pointer to a method compatible with usual calling convention.
--
Waldek Hebisch
[EMAIL PROTECTED]
something
like:
case FLOAT_EXPR:
CASE_FFS_EXPR
with `CASE_FFS_EXPR' expanding to nothing for new backend.
--
Waldek Hebisch
[EMAIL PROTECTED]
uld
still be more total work then to have direct backend support.
--
Waldek Hebisch
[EMAIL PROTECTED]
> On Wed, 2 Mar 2005, Waldek Hebisch wrote:
>
> > > If GPC developers are interested in having GPC integrated in GCC 4.1 and
> > > are willing to have it play by the same rules as the rest of GCC - note
> > > that the Ada maintainers made substantial changes to h
and merged as such).
ATM GPC does not use version control. Frank Heckenbach just periodically
collects flowing patches and his changes into releases.
--
Waldek Hebisch
[EMAIL PROTECTED]
13 matches
Mail list logo