From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: oszibarack korte <korte.oszibarack@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: PROBLEM !!! __ OS: ANY LINUX __ COMPILERS: gcc & g++ __ OUTPUT: BAD!!!
Date: Thu, 16 Mar 2023 17:49:40 +0000 [thread overview]
Message-ID: <CAH6eHdRW9DsMrJ2nxfz_YOGj5VeN4RbuB90rsMsW=5ktNtb9kw@mail.gmail.com> (raw)
In-Reply-To: <CAOxG7SLVq=nG9WvsC-BCUYrMm9PzWvd=yG+=+tuW-e79DbPt2w@mail.gmail.com>
On Thu, 16 Mar 2023 at 17:45, oszibarack korte via Gcc <gcc@gcc.gnu.org> wrote:
>
> *An unsolved problem for more than a decade!*
> *Dear GNU Compiler Collection development team!*
>
> *There is a problem with the gcc and g++ compilers for Linux operating
> systems!*
> *Here are 3 pieces of C and 3 pieces of C++ source code.*
>
>
>
>
>
> *- Please compile them on any LINUX!- Run it!- Compare the output with the
> corresponding source code!Summary: THE OUTPUTS ARE BAD !!!*
No, your programs are bad. You need to flush the output if you want it
to appear right away. When writing to standard output, a new line will
cause that to happen.
prev parent reply other threads:[~2023-03-16 17:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 17:44 oszibarack korte
2023-03-16 17:49 ` Andrew Pinski
2023-03-16 17:49 ` Jonathan Wakely [this message]
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='CAH6eHdRW9DsMrJ2nxfz_YOGj5VeN4RbuB90rsMsW=5ktNtb9kw@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=korte.oszibarack@gmail.com \
/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).