Linux PARISC architecture development
 help / color / mirror / Atom feed
From: joel.soete@freebel.net
To: joel.soete@freebel.net
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>,
	joel.soete@freebel.net, parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] gcc-cvs problem
Date: Mon, 03 Jun 2002 19:09:40 +0200 (CEST)	[thread overview]
Message-ID: <1023124180.3cfba2d4dc38b@webmail.tiscalinet.be> (raw)
In-Reply-To: <1023116322.3cfb842218471@webmail.tiscalinet.be>

Dave,

I really have no chance with this b2000:
I broken first my install and now it makes a HPMC in the middle of binutils
build and the pim info are not clear :((

So I will have to ask to HP to analyse those pim and eventually repare it.
(I hoppe we have a maintenance contract for this server)

Joel

Quoting joel.soete@freebel.net:

> Dave,
> 
> Quoting John David Anglin <dave@hiauly1.hia.nrc.ca>:
> 
> > > It seems to be well comited in last cvs update this morming I got
> in
> > > src/gcc/gcc/fixinc/inclhack.def:
> > > ...
> > > /*
> > >  * __thread is now a keyword.
> > >  */
> > 
> > > But do not seems to be applied as I got the same error?
> > > 
> > > What do I wrong or forget to do?
> > 
> > You should see the following in your build output:
> > 
> > Applying thread_keyword           to pthread.h
> > Fixed:  pthread.h
> 
> It stand well in my log files and here is the result:
> in {build}/gcc/include/pthread.h
> ...
> /* Create a thread with given attributes ATTR (or default attributes
>    if ATTR is NULL), and call function START_ROUTINE with given
>    arguments ARG.  */
> extern int pthread_create (pthread_t *__restrict __thr,
>                            __const pthread_attr_t *__restrict __attr,
>                            void *(*__start_routine) (void *),
>                            void *__restrict __arg) __THROW;
> ...
> 
> Which seems to be the desired patch?
> 
> Hmm... In what changing parameter name from __thread to __thr in such
> function
> prototype does matter (exepted if there is a border effect with some
> #define
> else where)? [afaik this name doe not matter for a C compiler?]
> 
> So I will have to go further to analyse precompile results.
> 
> See you next,
>     Joel
> 
> 
> -------------------------------------------------
> This mail sent through Tiscali Webmail (http://webmail.tiscali.be)
> 
> 


-------------------------------------------------
This mail sent through Tiscali Webmail (http://webmail.tiscali.be)

  parent reply	other threads:[~2002-06-03 17:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-30 17:22 [parisc-linux] gcc-cvs problem joel.soete
2002-05-30 17:51 ` John David Anglin
2002-05-31 15:14   ` joel.soete
2002-05-31 17:15     ` John David Anglin
2002-06-01 19:11       ` Joel Soete
2002-06-02  0:45         ` John David Anglin
2002-06-03 15:47           ` joel.soete
2002-06-03 14:58       ` joel.soete
2002-06-03 15:12         ` John David Anglin
2002-06-03 17:09         ` joel.soete [this message]
2002-06-03 17:38           ` John David Anglin
2002-06-04  6:32             ` joel.soete
2002-06-04 16:52               ` joel.soete
2002-06-05 16:11               ` joel.soete
2002-06-05 17:17       ` joel.soete
2002-06-05 17:34         ` John David Anglin

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=1023124180.3cfba2d4dc38b@webmail.tiscalinet.be \
    --to=joel.soete@freebel.net \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=parisc-linux@parisc-linux.org \
    /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