public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug ada/9535] Datagram socket semantics are wrong
[not found] <bug-9535-303@http.gcc.gnu.org/bugzilla/>
@ 2008-04-16 10:32 ` sam at gcc dot gnu dot org
2009-10-02 21:17 ` sam at gcc dot gnu dot org
1 sibling, 0 replies; 6+ messages in thread
From: sam at gcc dot gnu dot org @ 2008-04-16 10:32 UTC (permalink / raw)
To: gcc-bugs
--
sam at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |sam at gcc dot gnu dot org
|dot org |
Status|NEW |ASSIGNED
Last reconfirmed|2003-05-27 18:18:57 |2008-04-16 10:32:14
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9535
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug ada/9535] Datagram socket semantics are wrong
[not found] <bug-9535-303@http.gcc.gnu.org/bugzilla/>
2008-04-16 10:32 ` [Bug ada/9535] Datagram socket semantics are wrong sam at gcc dot gnu dot org
@ 2009-10-02 21:17 ` sam at gcc dot gnu dot org
1 sibling, 0 replies; 6+ messages in thread
From: sam at gcc dot gnu dot org @ 2009-10-02 21:17 UTC (permalink / raw)
To: gcc-bugs
------- Comment #7 from sam at gcc dot gnu dot org 2009-10-02 21:16 -------
The problem is still present in the trunk: datagram based streams are
meaningless in most cases.
The more I think about it, the more I think they should be removed from
GNAT.Sockets completely instead of half-fixed.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9535
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug ada/9535] Datagram socket semantics are wrong
[not found] <bug-9535-4@http.gcc.gnu.org/bugzilla/>
2014-05-21 12:50 ` charlet at gcc dot gnu.org
@ 2014-05-21 12:51 ` charlet at gcc dot gnu.org
1 sibling, 0 replies; 6+ messages in thread
From: charlet at gcc dot gnu.org @ 2014-05-21 12:51 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=9535
Arnaud Charlet <charlet at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |4.10.0
--- Comment #10 from Arnaud Charlet <charlet at gcc dot gnu.org> ---
Closing
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug ada/9535] Datagram socket semantics are wrong
[not found] <bug-9535-4@http.gcc.gnu.org/bugzilla/>
@ 2014-05-21 12:50 ` charlet at gcc dot gnu.org
2014-05-21 12:51 ` charlet at gcc dot gnu.org
1 sibling, 0 replies; 6+ messages in thread
From: charlet at gcc dot gnu.org @ 2014-05-21 12:50 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=9535
--- Comment #9 from Arnaud Charlet <charlet at gcc dot gnu.org> ---
Author: charlet
Date: Wed May 21 12:49:24 2014
New Revision: 210698
URL: http://gcc.gnu.org/viewcvs?rev=210698&root=gcc&view=rev
Log:
Previous change (rev 210697) should have mentioned PR ada/9535:
PR ada/9535
* g-socket.adb (Read and Write for Datagram_Socket_Stream_Type):
Provide a behaviour more consistent with underlying datagram
socket: do not attempt to loop over Send_Socket/Receive_Socket
iterating along the buffer.
Modified:
trunk/gcc/ada/ChangeLog
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug ada/9535] Datagram socket semantics are wrong
[not found] <20030201180601.9535.simon@pushface.org>
2003-05-27 18:24 ` fw@gcc.gnu.org
@ 2003-06-22 3:27 ` pinskia at physics dot uc dot edu
1 sibling, 0 replies; 6+ messages in thread
From: pinskia at physics dot uc dot edu @ 2003-06-22 3:27 UTC (permalink / raw)
To: gcc-bugs
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9535
pinskia at physics dot uc dot edu changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|3.4 |---
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug ada/9535] Datagram socket semantics are wrong
[not found] <20030201180601.9535.simon@pushface.org>
@ 2003-05-27 18:24 ` fw@gcc.gnu.org
2003-06-22 3:27 ` pinskia at physics dot uc dot edu
1 sibling, 0 replies; 6+ messages in thread
From: fw@gcc.gnu.org @ 2003-05-27 18:24 UTC (permalink / raw)
To: gcc-bugs
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9535
fw@gcc.gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|major |normal
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
Last reconfirmed|0000-00-00 00:00:00 |2003-05-27 18:18:57
date| |
------- Additional Comments From fw@gcc.gnu.org 2003-05-27 18:18 -------
IMHO, the changes should be made specific to datagram sockets (UDP).
Current semantics are acceptable for stream sockets (TCP) and match
expectations Ada programmers might have about Read/Write operations.
The Write fix seems questionable: The caller cannot know if a packet has
been sent or not.
However, Ada streams are inherently biased towards reliable,
stream-based data transmission. It is quite hard to use them for
anything else.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2014-05-21 12:51 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-9535-303@http.gcc.gnu.org/bugzilla/>
2008-04-16 10:32 ` [Bug ada/9535] Datagram socket semantics are wrong sam at gcc dot gnu dot org
2009-10-02 21:17 ` sam at gcc dot gnu dot org
[not found] <bug-9535-4@http.gcc.gnu.org/bugzilla/>
2014-05-21 12:50 ` charlet at gcc dot gnu.org
2014-05-21 12:51 ` charlet at gcc dot gnu.org
[not found] <20030201180601.9535.simon@pushface.org>
2003-05-27 18:24 ` fw@gcc.gnu.org
2003-06-22 3:27 ` pinskia at physics dot uc dot edu
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).