public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: "gkourtis@freemail.gr" <gkourtis@freemail.gr>
Cc: gcc-help@gnu.org
Subject: Re: Bug? Why __seg_fs __seg_gs are visible while compiling through gcc and not while compiling through g++ (error) even if the statements are enclosed in 'extern "C" {...}' statements
Date: Sun, 16 Jul 2023 21:28:07 +0800	[thread overview]
Message-ID: <0fa24da43696288758bc62faa9a060cc8808712e.camel@xry111.site> (raw)
In-Reply-To: <c3afdfb9-dc97-76fc-b7c4-c762a84f33cb@freemail.gr>

On Sun, 2023-07-16 at 12:42 +0300, gkourtis@freemail.gr wrote:
> Thanks for pointing out the known problem.
> By the way what should I have done on my own to detect the "known
> issue" ?
> As I did various searches without any result !

Use the "search" box at https://gcc.gnu.org/bugzilla/.

> George
> 
> Στις 15/7/23 16:08, ο/η Xi Ruoyao έγραψε:
> > On Sat, 2023-07-15 at 16:01 +0300, gkourtis--- via Gcc-help wrote:
> > > I think there is some sort of bug !!!
> > > 
> > > When I compile throught gcc __seg_gs is visible, while if I use
> > > g++ it
> > > is not !!!
> > > 
> > > Should it be like that ?
> > https://gcc.gnu.org/PR69549
> > 
> 

-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University

  parent reply	other threads:[~2023-07-16 13:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-15 13:01 gkourtis
2023-07-15 13:08 ` Xi Ruoyao
     [not found]   ` <c3afdfb9-dc97-76fc-b7c4-c762a84f33cb@freemail.gr>
2023-07-16 13:28     ` Xi Ruoyao [this message]
2023-07-15 19:55 ` Jonathan Wakely

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=0fa24da43696288758bc62faa9a060cc8808712e.camel@xry111.site \
    --to=xry111@xry111.site \
    --cc=gcc-help@gnu.org \
    --cc=gkourtis@freemail.gr \
    /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).