Linux PARISC architecture development
 help / color / mirror / Atom feed
From: joel.soete@freebel.net
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: Joel Soete <joel.soete@freebel.net>, parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] gcc-cvs problem
Date: Mon, 03 Jun 2002 17:47:13 +0200 (CEST)	[thread overview]
Message-ID: <1023119233.3cfb8f8180cd6@webmail.tiscalinet.be> (raw)
In-Reply-To: <200206020045.g520jQ6K009698@hiauly1.hia.nrc.ca>

Quoting John David Anglin <dave@hiauly1.hia.nrc.ca>:

> > I will have a detailed look but as newbee in gcc stuff it will take a
> time.
> 
> If you manually execute the failing compilation command changing '-c'
> to '-E', this will generate the cpp processed output for the
> compilation
> source file.

Hey I also had to do it when I tried and succed to port f2c with bcc 31 (ten
years ago already ;)

>  Inspection of this output should allow you to see exactly
> which include files have been loaded and the result of all macro
> expansions.

and here is the only pthread_create expansion I found in the output file:
# 163 "../linuxthreads/sysdeps/pthread/pthread.h"
extern int pthread_create (pthread_t *__restrict __thread,
                           __const pthread_attr_t *__restrict __attr,
                           void *(*__start_routine) (void *),
                           void *__restrict __arg) ;

So I will change manually __thread by __thr and see.

I also find glibc cvs and co and the new version of 

${src}/glibc/linuxthreads/sysdeps/pthread/pthread.h replace also __thread by
__threadp. Curious?

Joel

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

  reply	other threads:[~2002-06-03 15:47 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 [this message]
2002-06-03 14:58       ` joel.soete
2002-06-03 15:12         ` John David Anglin
2002-06-03 17:09         ` joel.soete
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=1023119233.3cfb8f8180cd6@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