* [PATCH v4] RISC-V: Extend .insn directive to support hardcode encoding.
@ 2021-07-16 5:32 Nelson Chu
2021-08-31 5:05 ` Nelson Chu
0 siblings, 1 reply; 2+ messages in thread
From: Nelson Chu @ 2021-07-16 5:32 UTC (permalink / raw)
To: binutils
Compared to v3,
1. Dump unrecognized instructions as .insn <value>, since mapping
symbols make sure that they are instructions.
2. Add document for two new .insn formats.
I think this patch should be committed after the mapping symbols
patch, since the above ponit 1.
Thanks
Nelson
==========================================================
The .insn directive can let users use their own instructions, or
some new instruction, which haven't supported in the old binutils.
For example, if users want to use sifive cache instruction, they
cannot just write "cflush.d1.l1" in the assembly code, they should
use ".insn i SYSTEM, 0, x0, x10, -0x40". But the .insn directive
may not easy to use for some cases, and not so friendly to users.
Therefore, I believe most of the users will use ".word 0xfc050073",
to encode the instructions directly, rather than use .insn. But
once we have supported the mapping symbols, the .word directives
are marked as data, so disassembler won't dump them as instructions
as usual. I have discussed this with Kito many times, we all think
extend the .insn direcitve to support the hardcode encoding, is the
easiest way to resolve the problem. Therefore, there are two more
.insn formats are proposed as follows,
(original) .insn <type>, <operand1>, <operand2>, ...
.insn <insn-length>, <value>
.insn <value>
The <type> is string, and the <insn-length> and <value> are constants.
gas/
* config/tc-riscv.c (riscv_ip_hardcode): Similar to riscv_ip,
but assembles an instruction according to the hardcode values
of .insn directive.
* doc/c-riscv.texi: Document two new .insn formats.
* testsuite/gas/riscv/insn-fail.d: New testcases.
* testsuite/gas/riscv/insn-fail.l: Likewise.
* testsuite/gas/riscv/insn-fail.s: Likewise.
* testsuite/gas/riscv/insn.d: Updated.
* testsuite/gas/riscv/insn.s: Likewise.
opcodes/
* riscv-dis.c (riscv_disassemble_insn): Dump unrecognized
instructions as .insn <value>, since mapping symbols make
sure that they are instructions.
Reviewed-by: Palmer Dabbelt <palmerdabbelt@google.com>
Reviewed-by: Kito Cheng <kito.cheng@sifive.com>
---
gas/config/tc-riscv.c | 57 +++++++++++++++++++++++++++++++++++--
gas/doc/c-riscv.texi | 14 +++++++--
gas/testsuite/gas/riscv/insn-fail.d | 3 ++
gas/testsuite/gas/riscv/insn-fail.l | 7 +++++
gas/testsuite/gas/riscv/insn-fail.s | 6 ++++
gas/testsuite/gas/riscv/insn.d | 6 ++++
gas/testsuite/gas/riscv/insn.s | 7 +++++
opcodes/riscv-dis.c | 2 +-
8 files changed, 96 insertions(+), 6 deletions(-)
create mode 100644 gas/testsuite/gas/riscv/insn-fail.d
create mode 100644 gas/testsuite/gas/riscv/insn-fail.l
create mode 100644 gas/testsuite/gas/riscv/insn-fail.s
diff --git a/gas/config/tc-riscv.c b/gas/config/tc-riscv.c
index 18379d2..b9c9ee2 100644
--- a/gas/config/tc-riscv.c
+++ b/gas/config/tc-riscv.c
@@ -2899,6 +2899,50 @@ riscv_ip (char *str, struct riscv_cl_insn *ip, expressionS *imm_expr,
return error;
}
+/* Similar to riscv_ip, but assembles an instruction according to the
+ hardcode values of .insn directive. */
+
+static const char *
+riscv_ip_hardcode (char *str,
+ struct riscv_cl_insn *ip,
+ expressionS *imm_expr,
+ const char *error)
+{
+ struct riscv_opcode *insn;
+ insn_t values[2] = {0, 0};
+ unsigned int num = 0;
+
+ input_line_pointer = str;
+ do
+ {
+ expression (imm_expr);
+ if (imm_expr->X_op != O_constant)
+ {
+ /* The first value isn't constant, so it should be
+ .insn <type> <operands>. Call riscv_ip to parse it. */
+ if (num == 0)
+ return error;
+ return _("values must be constant");
+ }
+ values[num++] = (insn_t) imm_expr->X_add_number;
+ }
+ while (*input_line_pointer++ == ',' && num < 2);
+
+ input_line_pointer--;
+ if (*input_line_pointer != '\0')
+ return _("unrecognized values");
+
+ insn = XNEW (struct riscv_opcode);
+ insn->match = values[num - 1];
+ create_insn (ip, insn);
+ unsigned int bytes = riscv_insn_length (insn->match);
+ if (values[num - 1] >> (8 * bytes) != 0
+ || (num == 2 && values[0] != bytes))
+ return _("value conflicts with instruction length");
+
+ return NULL;
+}
+
void
md_assemble (char *str)
{
@@ -3891,7 +3935,10 @@ s_riscv_leb128 (int sign)
return s_leb128 (sign);
}
-/* Parse the .insn directive. */
+/* Parse the .insn directive. There are three formats,
+ Format 1: .insn <type> <operand1>, <operand2>, ...
+ Format 2: .insn <length>, <value>
+ Format 3: .insn <value>. */
static void
s_riscv_insn (int x ATTRIBUTE_UNUSED)
@@ -3912,11 +3959,15 @@ s_riscv_insn (int x ATTRIBUTE_UNUSED)
const char *error = riscv_ip (str, &insn, &imm_expr,
&imm_reloc, insn_type_hash);
-
if (error)
{
- as_bad ("%s `%s'", error, str);
+ char *save_in = input_line_pointer;
+ error = riscv_ip_hardcode (str, &insn, &imm_expr, error);
+ input_line_pointer = save_in;
}
+
+ if (error)
+ as_bad ("%s `%s'", error, str);
else
{
gas_assert (insn.insn_mo->pinfo != INSN_MACRO);
diff --git a/gas/doc/c-riscv.texi b/gas/doc/c-riscv.texi
index c15297e..bfbf61d 100644
--- a/gas/doc/c-riscv.texi
+++ b/gas/doc/c-riscv.texi
@@ -213,13 +213,23 @@ desirable.
Enables or disables the CSR checking.
@cindex INSN directives
-@item .insn @var{value}
+@item .insn @var{type}, @var{operand} [,...,@var{operand_n}]
+@itemx .insn @var{insn_length}, @var{value}
@itemx .insn @var{value}
This directive permits the numeric representation of an instructions
and makes the assembler insert the operands according to one of the
instruction formats for @samp{.insn} (@ref{RISC-V-Formats}).
For example, the instruction @samp{add a0, a1, a2} could be written as
-@samp{.insn r 0x33, 0, 0, a0, a1, a2}.
+@samp{.insn r 0x33, 0, 0, a0, a1, a2}. But in fact, the instruction
+formats are difficult to use for some users, so most of them are using
+@samp{.word} to encode the instruction directly, rather than using
+@samp{.insn}. It is fine for now, but will be wrong when the mapping
+symbols are supported, since @samp{.word} will not be shown as an
+instruction, it should be shown as data. Therefore, we also support
+two more formats of the @samp{.insn}, the instruction @samp{add a0, a1, a2}
+could also be written as @samp{.insn 0x4, 0xc58533} or @samp{.insn 0xc58533}.
+When the @var{insn_length} is set, then assembler will check if the
+@var{value} is a valid @var{insn_length} bytes instruction.
@cindex @code{.attribute} directive, RISC-V
@item .attribute @var{tag}, @var{value}
diff --git a/gas/testsuite/gas/riscv/insn-fail.d b/gas/testsuite/gas/riscv/insn-fail.d
new file mode 100644
index 0000000..3548e85
--- /dev/null
+++ b/gas/testsuite/gas/riscv/insn-fail.d
@@ -0,0 +1,3 @@
+#as:
+#source: insn-fail.s
+#error_output: insn-fail.l
diff --git a/gas/testsuite/gas/riscv/insn-fail.l b/gas/testsuite/gas/riscv/insn-fail.l
new file mode 100644
index 0000000..e47d106
--- /dev/null
+++ b/gas/testsuite/gas/riscv/insn-fail.l
@@ -0,0 +1,7 @@
+.*Assembler messages:
+.*Error: unrecognized opcode `r,0x00000013'
+.*Error: values must be constant `0x4,rs1'
+.*Error: unrecognized values `0x4 0x5'
+.*Error: unrecognized values `0x4,0x5,0x6'
+.*Error: value conflicts with instruction length `0x4,0x0001'
+.*Error: value conflicts with instruction length `0x2,0x00000013'
diff --git a/gas/testsuite/gas/riscv/insn-fail.s b/gas/testsuite/gas/riscv/insn-fail.s
new file mode 100644
index 0000000..064211d
--- /dev/null
+++ b/gas/testsuite/gas/riscv/insn-fail.s
@@ -0,0 +1,6 @@
+ .insn r, 0x00000013
+ .insn 0x4, rs1
+ .insn 0x4 0x5
+ .insn 0x4, 0x5, 0x6
+ .insn 0x4, 0x0001
+ .insn 0x2, 0x00000013
diff --git a/gas/testsuite/gas/riscv/insn.d b/gas/testsuite/gas/riscv/insn.d
index 8cb3d64..286d8c3 100644
--- a/gas/testsuite/gas/riscv/insn.d
+++ b/gas/testsuite/gas/riscv/insn.d
@@ -69,3 +69,9 @@ Disassembly of section .text:
[^:]+:[ ]+00c58533[ ]+add[ ]+a0,a1,a2
[^:]+:[ ]+00c58533[ ]+add[ ]+a0,a1,a2
[^:]+:[ ]+00c58533[ ]+add[ ]+a0,a1,a2
+[^:]+:[ ]+0001[ ]+nop
+[^:]+:[ ]+00000013[ ]+nop
+[^:]+:[ ]+00000057[ ]+.insn[ ]+0x57
+[^:]+:[ ]+0001[ ]+nop
+[^:]+:[ ]+00000013[ ]+nop
+[^:]+:[ ]+00000057[ ]+.insn[ ]+0x57
diff --git a/gas/testsuite/gas/riscv/insn.s b/gas/testsuite/gas/riscv/insn.s
index 937ad11..8473905 100644
--- a/gas/testsuite/gas/riscv/insn.s
+++ b/gas/testsuite/gas/riscv/insn.s
@@ -53,3 +53,10 @@ target:
.insn r 0x33, 0, 0, fa0, a1, fa2
.insn r 0x33, 0, 0, a0, fa1, fa2
.insn r 0x33, 0, 0, fa0, fa1, fa2
+
+ .insn 0x0001
+ .insn 0x00000013
+ .insn 0x00000057
+ .insn 0x2, 0x0001
+ .insn 0x4, 0x00000013
+ .insn 0x4, 0x00000057
diff --git a/opcodes/riscv-dis.c b/opcodes/riscv-dis.c
index 2df8edc..6f2adda 100644
--- a/opcodes/riscv-dis.c
+++ b/opcodes/riscv-dis.c
@@ -557,7 +557,7 @@ riscv_disassemble_insn (bfd_vma memaddr, insn_t word, disassemble_info *info)
/* We did not find a match, so just print the instruction bits. */
info->insn_type = dis_noninsn;
- (*info->fprintf_func) (info->stream, "0x%llx", (unsigned long long)word);
+ (*info->fprintf_func) (info->stream, ".insn\t0x%llx", (unsigned long long)word);
return insnlen;
}
--
2.7.4
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH v4] RISC-V: Extend .insn directive to support hardcode encoding.
2021-07-16 5:32 [PATCH v4] RISC-V: Extend .insn directive to support hardcode encoding Nelson Chu
@ 2021-08-31 5:05 ` Nelson Chu
0 siblings, 0 replies; 2+ messages in thread
From: Nelson Chu @ 2021-08-31 5:05 UTC (permalink / raw)
To: Binutils
Hi Guys,
Committed this patch according to our previous plan, since mapping
symbols are supported in mainline for now. Just that,
> 1. Dump unrecognized instructions as .insn <value>, since mapping
> symbols make sure that they are instructions.
We probably need to dump the unrecognized instructions just like
before - dump it without the .insn prefix, while the objects don't
have any mapping symbols. Besides, I'm not sure if this change may
cause gdb or other tools to fail. Anyway, I decided to remove it from
the patch for now, and then deal with it later.
Thanks
Nelson
On Fri, Jul 16, 2021 at 1:32 PM Nelson Chu <nelson.chu@sifive.com> wrote:
>
> Compared to v3,
> 1. Dump unrecognized instructions as .insn <value>, since mapping
> symbols make sure that they are instructions.
> 2. Add document for two new .insn formats.
>
> I think this patch should be committed after the mapping symbols
> patch, since the above ponit 1.
>
> Thanks
> Nelson
>
> ==========================================================
>
> The .insn directive can let users use their own instructions, or
> some new instruction, which haven't supported in the old binutils.
> For example, if users want to use sifive cache instruction, they
> cannot just write "cflush.d1.l1" in the assembly code, they should
> use ".insn i SYSTEM, 0, x0, x10, -0x40". But the .insn directive
> may not easy to use for some cases, and not so friendly to users.
> Therefore, I believe most of the users will use ".word 0xfc050073",
> to encode the instructions directly, rather than use .insn. But
> once we have supported the mapping symbols, the .word directives
> are marked as data, so disassembler won't dump them as instructions
> as usual. I have discussed this with Kito many times, we all think
> extend the .insn direcitve to support the hardcode encoding, is the
> easiest way to resolve the problem. Therefore, there are two more
> .insn formats are proposed as follows,
>
> (original) .insn <type>, <operand1>, <operand2>, ...
> .insn <insn-length>, <value>
> .insn <value>
>
> The <type> is string, and the <insn-length> and <value> are constants.
>
> gas/
> * config/tc-riscv.c (riscv_ip_hardcode): Similar to riscv_ip,
> but assembles an instruction according to the hardcode values
> of .insn directive.
> * doc/c-riscv.texi: Document two new .insn formats.
> * testsuite/gas/riscv/insn-fail.d: New testcases.
> * testsuite/gas/riscv/insn-fail.l: Likewise.
> * testsuite/gas/riscv/insn-fail.s: Likewise.
> * testsuite/gas/riscv/insn.d: Updated.
> * testsuite/gas/riscv/insn.s: Likewise.
> opcodes/
> * riscv-dis.c (riscv_disassemble_insn): Dump unrecognized
> instructions as .insn <value>, since mapping symbols make
> sure that they are instructions.
>
> Reviewed-by: Palmer Dabbelt <palmerdabbelt@google.com>
> Reviewed-by: Kito Cheng <kito.cheng@sifive.com>
> ---
> gas/config/tc-riscv.c | 57 +++++++++++++++++++++++++++++++++++--
> gas/doc/c-riscv.texi | 14 +++++++--
> gas/testsuite/gas/riscv/insn-fail.d | 3 ++
> gas/testsuite/gas/riscv/insn-fail.l | 7 +++++
> gas/testsuite/gas/riscv/insn-fail.s | 6 ++++
> gas/testsuite/gas/riscv/insn.d | 6 ++++
> gas/testsuite/gas/riscv/insn.s | 7 +++++
> opcodes/riscv-dis.c | 2 +-
> 8 files changed, 96 insertions(+), 6 deletions(-)
> create mode 100644 gas/testsuite/gas/riscv/insn-fail.d
> create mode 100644 gas/testsuite/gas/riscv/insn-fail.l
> create mode 100644 gas/testsuite/gas/riscv/insn-fail.s
>
> diff --git a/gas/config/tc-riscv.c b/gas/config/tc-riscv.c
> index 18379d2..b9c9ee2 100644
> --- a/gas/config/tc-riscv.c
> +++ b/gas/config/tc-riscv.c
> @@ -2899,6 +2899,50 @@ riscv_ip (char *str, struct riscv_cl_insn *ip, expressionS *imm_expr,
> return error;
> }
>
> +/* Similar to riscv_ip, but assembles an instruction according to the
> + hardcode values of .insn directive. */
> +
> +static const char *
> +riscv_ip_hardcode (char *str,
> + struct riscv_cl_insn *ip,
> + expressionS *imm_expr,
> + const char *error)
> +{
> + struct riscv_opcode *insn;
> + insn_t values[2] = {0, 0};
> + unsigned int num = 0;
> +
> + input_line_pointer = str;
> + do
> + {
> + expression (imm_expr);
> + if (imm_expr->X_op != O_constant)
> + {
> + /* The first value isn't constant, so it should be
> + .insn <type> <operands>. Call riscv_ip to parse it. */
> + if (num == 0)
> + return error;
> + return _("values must be constant");
> + }
> + values[num++] = (insn_t) imm_expr->X_add_number;
> + }
> + while (*input_line_pointer++ == ',' && num < 2);
> +
> + input_line_pointer--;
> + if (*input_line_pointer != '\0')
> + return _("unrecognized values");
> +
> + insn = XNEW (struct riscv_opcode);
> + insn->match = values[num - 1];
> + create_insn (ip, insn);
> + unsigned int bytes = riscv_insn_length (insn->match);
> + if (values[num - 1] >> (8 * bytes) != 0
> + || (num == 2 && values[0] != bytes))
> + return _("value conflicts with instruction length");
> +
> + return NULL;
> +}
> +
> void
> md_assemble (char *str)
> {
> @@ -3891,7 +3935,10 @@ s_riscv_leb128 (int sign)
> return s_leb128 (sign);
> }
>
> -/* Parse the .insn directive. */
> +/* Parse the .insn directive. There are three formats,
> + Format 1: .insn <type> <operand1>, <operand2>, ...
> + Format 2: .insn <length>, <value>
> + Format 3: .insn <value>. */
>
> static void
> s_riscv_insn (int x ATTRIBUTE_UNUSED)
> @@ -3912,11 +3959,15 @@ s_riscv_insn (int x ATTRIBUTE_UNUSED)
>
> const char *error = riscv_ip (str, &insn, &imm_expr,
> &imm_reloc, insn_type_hash);
> -
> if (error)
> {
> - as_bad ("%s `%s'", error, str);
> + char *save_in = input_line_pointer;
> + error = riscv_ip_hardcode (str, &insn, &imm_expr, error);
> + input_line_pointer = save_in;
> }
> +
> + if (error)
> + as_bad ("%s `%s'", error, str);
> else
> {
> gas_assert (insn.insn_mo->pinfo != INSN_MACRO);
> diff --git a/gas/doc/c-riscv.texi b/gas/doc/c-riscv.texi
> index c15297e..bfbf61d 100644
> --- a/gas/doc/c-riscv.texi
> +++ b/gas/doc/c-riscv.texi
> @@ -213,13 +213,23 @@ desirable.
> Enables or disables the CSR checking.
>
> @cindex INSN directives
> -@item .insn @var{value}
> +@item .insn @var{type}, @var{operand} [,...,@var{operand_n}]
> +@itemx .insn @var{insn_length}, @var{value}
> @itemx .insn @var{value}
> This directive permits the numeric representation of an instructions
> and makes the assembler insert the operands according to one of the
> instruction formats for @samp{.insn} (@ref{RISC-V-Formats}).
> For example, the instruction @samp{add a0, a1, a2} could be written as
> -@samp{.insn r 0x33, 0, 0, a0, a1, a2}.
> +@samp{.insn r 0x33, 0, 0, a0, a1, a2}. But in fact, the instruction
> +formats are difficult to use for some users, so most of them are using
> +@samp{.word} to encode the instruction directly, rather than using
> +@samp{.insn}. It is fine for now, but will be wrong when the mapping
> +symbols are supported, since @samp{.word} will not be shown as an
> +instruction, it should be shown as data. Therefore, we also support
> +two more formats of the @samp{.insn}, the instruction @samp{add a0, a1, a2}
> +could also be written as @samp{.insn 0x4, 0xc58533} or @samp{.insn 0xc58533}.
> +When the @var{insn_length} is set, then assembler will check if the
> +@var{value} is a valid @var{insn_length} bytes instruction.
>
> @cindex @code{.attribute} directive, RISC-V
> @item .attribute @var{tag}, @var{value}
> diff --git a/gas/testsuite/gas/riscv/insn-fail.d b/gas/testsuite/gas/riscv/insn-fail.d
> new file mode 100644
> index 0000000..3548e85
> --- /dev/null
> +++ b/gas/testsuite/gas/riscv/insn-fail.d
> @@ -0,0 +1,3 @@
> +#as:
> +#source: insn-fail.s
> +#error_output: insn-fail.l
> diff --git a/gas/testsuite/gas/riscv/insn-fail.l b/gas/testsuite/gas/riscv/insn-fail.l
> new file mode 100644
> index 0000000..e47d106
> --- /dev/null
> +++ b/gas/testsuite/gas/riscv/insn-fail.l
> @@ -0,0 +1,7 @@
> +.*Assembler messages:
> +.*Error: unrecognized opcode `r,0x00000013'
> +.*Error: values must be constant `0x4,rs1'
> +.*Error: unrecognized values `0x4 0x5'
> +.*Error: unrecognized values `0x4,0x5,0x6'
> +.*Error: value conflicts with instruction length `0x4,0x0001'
> +.*Error: value conflicts with instruction length `0x2,0x00000013'
> diff --git a/gas/testsuite/gas/riscv/insn-fail.s b/gas/testsuite/gas/riscv/insn-fail.s
> new file mode 100644
> index 0000000..064211d
> --- /dev/null
> +++ b/gas/testsuite/gas/riscv/insn-fail.s
> @@ -0,0 +1,6 @@
> + .insn r, 0x00000013
> + .insn 0x4, rs1
> + .insn 0x4 0x5
> + .insn 0x4, 0x5, 0x6
> + .insn 0x4, 0x0001
> + .insn 0x2, 0x00000013
> diff --git a/gas/testsuite/gas/riscv/insn.d b/gas/testsuite/gas/riscv/insn.d
> index 8cb3d64..286d8c3 100644
> --- a/gas/testsuite/gas/riscv/insn.d
> +++ b/gas/testsuite/gas/riscv/insn.d
> @@ -69,3 +69,9 @@ Disassembly of section .text:
> [^:]+:[ ]+00c58533[ ]+add[ ]+a0,a1,a2
> [^:]+:[ ]+00c58533[ ]+add[ ]+a0,a1,a2
> [^:]+:[ ]+00c58533[ ]+add[ ]+a0,a1,a2
> +[^:]+:[ ]+0001[ ]+nop
> +[^:]+:[ ]+00000013[ ]+nop
> +[^:]+:[ ]+00000057[ ]+.insn[ ]+0x57
> +[^:]+:[ ]+0001[ ]+nop
> +[^:]+:[ ]+00000013[ ]+nop
> +[^:]+:[ ]+00000057[ ]+.insn[ ]+0x57
> diff --git a/gas/testsuite/gas/riscv/insn.s b/gas/testsuite/gas/riscv/insn.s
> index 937ad11..8473905 100644
> --- a/gas/testsuite/gas/riscv/insn.s
> +++ b/gas/testsuite/gas/riscv/insn.s
> @@ -53,3 +53,10 @@ target:
> .insn r 0x33, 0, 0, fa0, a1, fa2
> .insn r 0x33, 0, 0, a0, fa1, fa2
> .insn r 0x33, 0, 0, fa0, fa1, fa2
> +
> + .insn 0x0001
> + .insn 0x00000013
> + .insn 0x00000057
> + .insn 0x2, 0x0001
> + .insn 0x4, 0x00000013
> + .insn 0x4, 0x00000057
> diff --git a/opcodes/riscv-dis.c b/opcodes/riscv-dis.c
> index 2df8edc..6f2adda 100644
> --- a/opcodes/riscv-dis.c
> +++ b/opcodes/riscv-dis.c
> @@ -557,7 +557,7 @@ riscv_disassemble_insn (bfd_vma memaddr, insn_t word, disassemble_info *info)
>
> /* We did not find a match, so just print the instruction bits. */
> info->insn_type = dis_noninsn;
> - (*info->fprintf_func) (info->stream, "0x%llx", (unsigned long long)word);
> + (*info->fprintf_func) (info->stream, ".insn\t0x%llx", (unsigned long long)word);
> return insnlen;
> }
>
> --
> 2.7.4
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-08-31 5:05 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-07-16 5:32 [PATCH v4] RISC-V: Extend .insn directive to support hardcode encoding Nelson Chu
2021-08-31 5:05 ` Nelson Chu
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).