X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
        bh=FtJ6FgCR/vjQhuW9JmECSsfaMx6aZzs3z4V3L1trxuM=;
        b=tT+frNeLwtdE7HpOBXw99dhO3D0Qd8CPY76rOQ5PJWTWWOxfRJkCn8rbb0OL6/Lfsj
         veJfdr0fNh9+g7XJLuep/hiAiildR86Zhi2IZiiYsdcpH//O0uWD5gLOmxF8zRemQlC9
         wdxdcpTJKLwMNqQxzbBssHACDAhXaM9nZaDOva2xIAf8JlUU+NP4Tm8z89CYvX6uz8Yn
         5TgaXwgqkSELwY3mE0FzhjUk1xECf1KHgYj3rRsSXFSgaJ7PT3nzrabk2xheaV2aDpDT
         xy6VwKAaNN3f3GhV6oIaYa7Qwy/nMTJompj4RoABT/9gtzMaQWQIG8IQku5+Aq1tmNew
         2BDQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:in-reply-to:references:from:date
         :message-id:subject:to;
        bh=FtJ6FgCR/vjQhuW9JmECSsfaMx6aZzs3z4V3L1trxuM=;
        b=Pu5P1WvWoOxYmZrOBgjj7HYTaHPaYES5ywOWYFY7No+WK00+Jk1JGLOjkUql0/vI3F
         ent1I2QgwZ4mGmZJJub9W+ydPGwAGD9h08k71lZd6R+JNAH47OWD7uGQ9sXuA/pSufwB
         rsu8unNFOFAVdunIUqbmQZhdkcS+z2UvgxyVwbm6l9BuDHer8wrAy4nyXSDoSRluYuej
         KB99YAdQhzrlThgWz96Ne5reI+lqZTdVrlJsiQUQBtEGUnmFnFrJGNlBTgs4Oj1myKYa
         2RxNRWs/da1ZUy2AxRWSKzfQiZJllEicVIKJlWim9KzFVFJUAOTaNa//WXCB/LltYxhO
         HTFw==
X-Gm-Message-State: AFeK/H2LzziFYKygyMJAo8nUfP0kbKptiuxjXgGI8W9Ep9kUXIVNmwM0ARMuselp8O5jNw5JPbe5cw9adj6TiA==
X-Received: by 10.46.82.208 with SMTP id n77mr2209170lje.56.1490724627192;
 Tue, 28 Mar 2017 11:10:27 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <CAPLG5jYr14gXSGKc45Zhre2j17oZYvYYxzuqDjS1+junGv3gug@mail.gmail.com>
References: <CAPLG5jZx4v-0QV+6F5xLALeQHGGiz2RUzkF3eOcYX7Y2MkiJGQ AT mail DOT gmail DOT com>
 <xnbmsl5odf DOT fsf AT envy DOT delorie DOT com> <CAPLG5jYr14gXSGKc45Zhre2j17oZYvYYxzuqDjS1+junGv3gug AT mail DOT gmail DOT com>
From: "J.W. Jagersma (jwjagersma AT gmail DOT com) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
Date: Tue, 28 Mar 2017 20:10:26 +0200
Message-ID: <CAPLG5jYiO7xca=e9myGo2K96t8gkaiOqUhNwVFjjU7Ho1rowNw@mail.gmail.com>
Subject: Re: using fs/gs segment registers in djgpp?
To: djgpp AT delorie DOT com
Content-Type: text/plain; charset=UTF-8
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

oops, I keep forgetting to add the cc...

On 28 March 2017 at 20:07, J.W. Jagersma <jwjagersma AT gmail DOT com> wrote:
> Alright. So do any of these functions make any assumptions about the
> contents of the extra segment registers? That's the main thing I was
> worried about. Making sure to restore fs/gs before accessing them
> shouldn't be a problem.
>
> On a somewhat related note, I was kinda hoping to use the new address
> space specifiers (__seg_fs and __seg_gs) that were introduced in gcc
> 6. But apparently those were never implemented on the c++ side...
>
> On 28 March 2017 at 18:59, DJ Delorie <dj AT delorie DOT com> wrote:
>>
>> The transfer buffer might use %fs or %gs, if so, any I/O, BIOS, or DOS
>> calls would touch those too.