From: Petri Latvala <petri.latvala@intel.com>
To: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 2/2] meson.build: Remove -fcommon flag
Date: Mon, 16 Jan 2023 11:30:50 +0200 [thread overview]
Message-ID: <Y8UZSlAv7X1N4COr@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20230113192553.89460-3-zbigniew.kempczynski@intel.com>
On Fri, Jan 13, 2023 at 08:25:53PM +0100, Zbigniew Kempczyński wrote:
> Ensure global variables are explicitly defined in one place and
> requires importing via extern keyword instead of duplicating definition
> resolved during linking time.
>
> Details: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85678
>
> Signed-off-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
> Cc: Petri Latvala <petri.latvala@intel.com>
> Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Reviewed-by: Petri Latvala <petri.latvala@intel.com>
> ---
> meson.build | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/meson.build b/meson.build
> index bbe1f673e8..7b25627229 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -70,7 +70,6 @@ cc_args = [
> # well with longjmp which is heavily used by IGT framework.
> '-fno-builtin-malloc',
> '-fno-builtin-calloc',
> - '-fcommon',
> ]
>
> foreach cc_arg : cc_args
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-01-16 9:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 19:25 [igt-dev] [PATCH i-g-t 0/2] Remove -fcommon flag Zbigniew Kempczyński
2023-01-13 19:25 ` [igt-dev] [PATCH i-g-t 1/2] lib/igt_crc: Remove crc32 table from common section Zbigniew Kempczyński
2023-01-16 9:29 ` Petri Latvala
2023-01-13 19:25 ` [igt-dev] [PATCH i-g-t 2/2] meson.build: Remove -fcommon flag Zbigniew Kempczyński
2023-01-16 9:30 ` Petri Latvala [this message]
2023-01-16 10:25 ` Zbigniew Kempczyński
2023-01-14 0:17 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-01-14 7:46 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
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=Y8UZSlAv7X1N4COr@platvala-desk.ger.corp.intel.com \
--to=petri.latvala@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=zbigniew.kempczynski@intel.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