public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Yong <jyong@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-3446] libgcc: Update 'gthr-mcf.h' to include a dedicated header for libobjc Date: Sun, 23 Oct 2022 02:00:37 +0000 (GMT) [thread overview] Message-ID: <20221023020037.B67123858D28@sourceware.org> (raw) https://gcc.gnu.org/g:0e37fd4dc74c1db99cdc7d71ef378e1221253c6f commit r13-3446-g0e37fd4dc74c1db99cdc7d71ef378e1221253c6f Author: LIU Hao <lh_mouse@126.com> Date: Sat Oct 22 17:31:46 2022 +0800 libgcc: Update 'gthr-mcf.h' to include a dedicated header for libobjc 'libobjc/thr.c' includes 'gthr.h'. While all the other gthread headers have `#ifdef _LIBOBJC` checks, and provide a different set of inline functions, I think having one header provide two completely unrelated set of APIs is unsatisfactory, complicates maintenance, and hinders further development. This commit references a new header for libobjc, and adds a copyright notice, as in other headers. libgcc/ChangeLog: * config/i386/gthr-mcf.h: Include 'gthr_libobjc.h' when building libobjc, instead of 'gthr.h' Diff: --- libgcc/config/i386/gthr-mcf.h | 35 +++++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+) diff --git a/libgcc/config/i386/gthr-mcf.h b/libgcc/config/i386/gthr-mcf.h index 58131bb7ca9..40da86802b6 100644 --- a/libgcc/config/i386/gthr-mcf.h +++ b/libgcc/config/i386/gthr-mcf.h @@ -1 +1,36 @@ +/* Threads compatibility routines for libgcc and libobjc. */ +/* Copyright (C) 2022 Free Software Foundation, Inc. + +This file is part of GCC. + +GCC is free software; you can redistribute it and/or modify it under +the terms of the GNU General Public License as published by the Free +Software Foundation; either version 3, or (at your option) any later +version. + +GCC is distributed in the hope that it will be useful, but WITHOUT ANY +WARRANTY; without even the implied warranty of MERCHANTABILITY or +FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License +for more details. + +Under Section 7 of GPL version 3, you are granted additional +permissions described in the GCC Runtime Library Exception, version +3.1, as published by the Free Software Foundation. + +You should have received a copy of the GNU General Public License and +a copy of the GCC Runtime Library Exception along with this program; +see the files COPYING3 and COPYING.RUNTIME respectively. If not, see +<http://www.gnu.org/licenses/>. */ + +#ifdef _LIBOBJC + +/* libobjc references some internal structures and requires a + * dedicated set of functions. */ +#include <mcfgthread/gthr_libobjc.h> + +#else /* _LIBOBJC */ + +/* This is for libgcc and libstdc++. */ #include <mcfgthread/gthr.h> + +#endif /* _LIBOBJC */
reply other threads:[~2022-10-23 2:00 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221023020037.B67123858D28@sourceware.org \ --to=jyong@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.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: linkBe 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).